OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

asap message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [asap] RE: ASAP

Also, consider the changes I provided in my wsdl at

For example, in http://easyasap.sourceforge.net/asap.wsdl
some syntax was corrected, namespace qualifications added, and
changestate, statechanged messages and operations were provided
and soapActions added.


Also, Jeff Cohen provided wsdl examples as well.
In some ways I think it might be good to have separate wsdl for different roles
to simplify use with UDDI.

On Oct 26, 2004, at 10:16 AM, Keith Swenson wrote:

one more time, with attachment.
Keith D Swenson, < kswenson at us . fujitsu . com >
Fujitsu Software Corporation
1250 E. Arques Avenue, Sunnyvale, CA 94085
(408) 746-6276 mobile: (408) 859-1005

-----Original Message-----
From: Keith Swenson [mailto:KSwenson@us.fujitsu.com]
Sent: Tuesday, October 26, 2004 7:02 AM
To: Zulfi Umrani
Cc: ASAP (asap@lists.oasis-open.org)
Subject: [asap] RE: ASAP

We did define a WSDL file, but hae not gotten it included in the spec yet. It is attached.

Each operation has a unique message in and out. This is consistent with the WS-I basic interoperability pattern.  Take a look at the WSDL and let me know if you still have questions.


> -----Original Message-----
> From: Zulfi Umrani [mailto:zumrani@novell.com]
> Sent: Monday, October 25, 2004 7:42 PM
> To: KSwenson@us.fujitsu.com
> Subject: ASAP
> Hi Keith,
> I went through the ASAP spec. I have a couple of questions. I
> will appreciate if you could answer them.
> Q.1: Why does ASAP spec not define WSDL interface for
> Observer, Factory and Instance?
> Q.2: In the typical scenario described in the spec, it is not
> described which operation(from WSDL perspective) is being
> invoked. I guess my question is how the operation information
> is conveyed using ASAP. Lets say that my service has 2
> operations "foo" and "bar" and both have different number and
> types of arguments(again from WSDL perspective), how would
> the service Instance know which operation, it has to start processing?
> Thanks,
> Zulfi

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]