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.
