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


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel-abstract message

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

Subject: Are WSDL descriptions always required for abstract processes

Title: Message
Dear  Abstract Colleagues,
I sent these questions to the main list back in April, but only received an initial response from Kevin (Liu).  Now this informal group is running I would like to ask again
Section 3  of the BPEL makes 'political' statements of direction with regard to the use of WSDL 1.1 - fair enough.  For an executable BPEL process there is clear need for the technical dependency on WSDL descriptions.  Not questioning that.
So my question is do all the WSDL descriptions have to be generated from the start, or can they be generated as part of the process of going from an abstract process description to an executable one?  If they are required for abstract processes as well then how many and which ones- see example below.
So to sum up what I am asking is:  What are the real requirements for, and dependencies on WSDL descriptions for the most abstract of *abstract* processes that BPEL allows?
I would like to see if there is a simple and agreed answer to this question or whether I should raise as an issue (or add in to an existing issue such as 82 or 97). 
 My question is:   Are WSDL descriptions *always* required for abstract processes.  Is the answer clear and correct in the specification? 
Imagine an process (A) that communicates with three remote processes (B), (C), (D).  Is it possible to produce an abstract process BPEL description on its own (one XML document) that conforms to the schema and to the letter and spirit of the textual specification, or is it required to always produce WSDL descriptions as well - if so how many and for what?  Three one for each of the 'A' ends of the A-B, A-C and A-D relationships, three one for each of the 'B', 'C' and 'D' ends of the A-B, A-C and A-D relationships respectively, or all of these making six in total? 
The spirit of section 15.1 (and especially the second paragraph) might be taken to suggest that the WSDL descriptions are not required. 
However, as Ugo has pointed out to me, the portType attribute is a qualified name type and is a required attribute on invoke, receive and reply, which implies that mechanistically the WDSL descriptions are required at present. 

Best Regards,


Tony Fletcher

Technical Advisor
Choreology Ltd.
68, Lombard Street, London EC3V 9L J   UK


+44 (0) 1473 729537


+44 (0) 7801 948219


+44 (0) 870 7390077




Business transaction management software for application coordination

Work: tony.fletcher@choreology.com

Home: amfletcher@iee.org


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