Support variable initialization per OASIS BPEL 2.0 spec
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM BPEL 1.1 GA
Reporter: Aleksander Adamowski
Assignee: Alejandro Guizar
OASIS Web Services Business Process Execution Language Version 2.0 specification, section
8.1, states that variables can be initialized upon definition:
"The syntax of the <variables> declaration is:
A variable can optionally be initialized by using an in-line from-spec. From-spec is
section 8.4. Conceptually the in-line variable initializations are modeled as a virtual
activity that contains a series of virtual <assign> activities, one for each
initialized, in the order they are listed in the variable declarations. The virtual
activities each contain a single virtual <copy> whose from-spec is as given in the
initialization and the to-spec points to the variable being created.
[SA00026] Variable initialization logic contained in scopes that contain or whose children
contain a start activity MUST only use idempotent functions in the from-spec. The use of
idempotent functions allows for all the values for such variables to be pre-computed and
on each process instance. "
The Eclipse BPEL Business Process Editor supports this - one can select a variable, and in
its properties panel choose "Initialization" tab, then e.g. specify From =
"Expression", Expression language = "Same as Process (XPath 1.0 in BPEL
2.0)" and input an expression.
Here's an example of such generated variable specification:
Unfortunately, jBPM BPEL ignores initialization from spec:
DEBUG [org.jbpm.context.exe.VariableContainer] create variable 'myVariable' in
'TokenVariableMap10d7fa4' with value '[myVariable: null]'
This feature of BPEL spec should be supported.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira