[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0
|
Hey Joni,
You are not on the latest version of
the BPEL 2.0 spec. (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html)
Here it says in chapter 8.4:
The from-spec MUST be one the following
variants:
<from
variable="BPELVariableName"
part="NCName"?>
<query
queryLanguage="anyURI"?>?
queryContent
</query>
</from>
<from
partnerLink="NCName"
endpointReference="myRole|partnerRole"
/>
<from
variable="BPELVariableName"
property="QName"
/>
<from
expressionLanguage="anyURI"?>_expression_</from>
<from><literal>literal
value</literal></from>
<from/>
That means that the following BPEL snippet
is correct:
<bpel:copy>
<bpel:from part="parameters"
variable="TravelBookingInput">
<bpel:query
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookRequest/startAirport]]></bpel:query>
</bpel:from>
<bpel:to part="parameters"
variable="TravelBookingOutput">
<bpel:query
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookResponse/startAirport]]></bpel:query>
</bpel:to>
</bpel:copy>
However you can also use the $-XPath-Syntax
to do the above assignment. (Use the "_expression_" option on the
assignment properties page to do this)
<bpel:copy>
<bpel:from expressionLanguage="...">$TravelBookingInput.parameters/TravelBookRequest/startAirport</bpel:from>
<bpel:to expressionLanguage="...">$TravelBookingOutput.parameters/TravelBookResponse/startAirport</bpel:to>
</bpel:copy>
(Assuming "TravelBookingInput"
and "TravelBookingOutput" are BPEL variables that point on WSDL
messages and "parameters" is a WSDL part within those messages...)
Mit freundlichen Grüßen / Kind regards
Michael Illiger
Software Developer - BPEL Editor
/ WID
IBM Software Group, Application
and Integration Middleware Software
WSS Business Process Solutions
Development 1
|
|
Phone:
| +49-7031-16-1273
| IBM Deutschland
|
|
E-Mail:
| milliger@xxxxxxxxxx
| Schoenaicher Str. 220
|
|
| 71032 Boeblingen
|
|
| Germany
|
|
|
IBM Deutschland Research
& Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294 |
From:
| Joni Lee <webcokies@xxxxxxxxx>
|
To:
| bpel-dev@xxxxxxxxxxx
|
Date:
| 11/24/2009 12:38 AM
|
Subject:
| [bpel-dev] The design tool different
from OASIS specification for BPEL2.0
|
Sent by:
| bpel-dev-bounces@xxxxxxxxxxx |
Hi,
As specified under 8.4 OASIS Specification:
http://www.oasis-open.org/apps/group_public/download.php/18714/#_Toc135660191
the from-spec MUST be one of the following variants:
<from variable="NCName" part="NCName"?/>
<from partnerLink="NCName" endpointReference="myRole|partnerRole"/>
<from variable="NCName" property="QName"/>
<from expressionLanguage="anyURI"?>_expression_</from>
<from><literal>literal value</literal></from>
--------------------------------------------------------------------------------------------------------
I've just install BPEL2.0 for Eclipse. When I make an assign of one variable
(messageType.part/query) to another variable (messageType.part/query),
the code are displayed in <from><query></query></from>,
which are not allowed in BPEL 2.0?
It has to be like this instead: <from>$message.part/query</from>
Or am I wrong with the 2.0 specification?
----------------------------------------------------------------------------------------------------------
<bpel:copy>
<bpel:from part="parameters"
variable="TravelBookingInput">
<bpel:query
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookRequest/startAirport]]></bpel:query>
</bpel:from>
<bpel:to part="parameters"
variable="TravelBookingOutput">
<bpel:query
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookResponse/startAirport]]></bpel:query>
</bpel:to>
</bpel:copy> |
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev