One of the big benefits of service-oriented architecture (SOA) development is that it approaches design from a business, as opposed to a technical, point of view. Unfortunately, SOA development projects can be more complicated than "regular" Java Platform, Enterprise Edition (Java EE) projects. With SOA projects, there are often more stakeholders, more disparate technologies to integrate, and more possible misunderstandings about overall project goals.
Welcome to BPEL XML.org.
This is the official community gathering place and information resource for the WS-BPEL OASIS Standard and related specifications. BPEL uses Web services standards to describe business process activities as Web services, defining how they can be composed to accomplish specific tasks. This is a community-driven site, and the public is encouraged to contribute content.
Implicit conversion of bpel:getVariableProperty(...)
Does the conversion of simple type values into XPath objects, as described for variables, apply for variable properties retrieved through bpel:getVariableProperty(...) in an XPath expression?
While I believe it is the intension to apply such a conversion, I cannot point out a requirement that enforces this -- did I miss it? However, the method signature returns “object”, suggesting that it may return an XPath object like Boolean for example. Also, an example in section 15.1.3 uses a boolean expression that expects an implicit conversion:
Oracle Magazine: Testing BPEL in the Real World
What expression or query will yield a variable reference?
In the specification, section 8.2.1 "Enclosing Elements", it says:
Evaluation of a WS-BPEL expression or query will yield one of the
following ...:
- a single XML infoset item ...
- a collection of XML infoset items ...
- a sequence of CIIs for simple type data ...
- a variable reference: e.g. <from>$myFooVar</from>
How can the context node point to an XPath object?
XPath 1.0 only accept a single node as the "context node", and it does not support XML Schema types, thus, any node value is an XPath string object.
Section 8.2.6:
"When XPath 1.0 is used as Query Language [...] If the type is a simple type, the context node MUST point to the XPath object specified in section 8.2.2"
Section 8.2.2:
IBM WebSphere® Integration Developer
IBM has been a long-supporter of BPEL, and numerous IBM products support BPEL as well.
WebSphere® Integration Developer
http://www-306.ibm.com/software/integration/wid/
WebSphere Integration Developer is a common tool for building SOA-based integration solutions across WebSphere Process Server, WebSphere ESB, and WebSphere Adapters. WID enables construction of process and integration solutions using drag-and-drop technology without having a working knowledge of Java. It enables rapid assembly of business solutions by wiring reusable service components.