[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5394) BPEL Plugin is not correctly initalizing variables
[
https://jira.jboss.org/jira/browse/JBIDE-5394?page=com.atlassian.jira.plu...
]
Brad Maxwell updated JBIDE-5394:
--------------------------------
Attachment: InvokeHelloWSBPEL.zip
Here is my test project, I deleted the Mapping in the AssignInput2HelloWSRequest, so you
can do the following to see the issue.
1) Select AssignInput2HelloWSRequest
2) Look in the Properties View
3) Select the Details tab in the Properties View
4) There should be no mappings
5) Click New
6) Create a Variable to Variable mapping
7) On the From side, expand the variable input / payload / input and select "input :
string"
8) On the To side, expand HelloWSPartnerRequest variable down and select "name:
string"
9) Click in the mappings area and it will prompt "Variable HelloWSPartnerRequest
doesn't have initializer. Should it be generated?"
10) Click Yes
11) Switch to the Source view of the Process
12) Search for this text:
<bpel:literal xml:space="preserve"><tns:hello
xmlns:tns="http://jboss.com/examples/ws/Hello"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
</tns:hello>
</bpel:literal>
13) This text is what the variable HelloWSPartnerRequest gets initialized to. When this
process is deployed in Riftsaw and run it results an the error mentioned before. The
error is that XPATH cannot find "name" in the HelloWSPartnerRequest to copy to.
I found that adding <name xmlns=""/> above the </tns:hello> resolves
the issue. So it seems the HelloWSPartnerRequest is not getting completely initialized.
14) Also I noticed that in the AssignHelloWSResponse2Output step, where I copy from the
HelloWSPartnerResponse / helloResponse / return to output / payload / result, that output
seems to get initialized correctly. Notice in the string below, the initializer created
has <tns:result></tns:result>
bpel:literal xml:space="preserve"><tns:InvokeHelloWSProcessResponse
xmlns:tns="http://jboss.com/bpel/InvokeHelloWS"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tns:result></tns:result>
</tns:InvokeHelloWSProcessResponse>
</bpel:literal>
Thanks,
Brad
BPEL Plugin is not correctly initalizing variables
--------------------------------------------------
Key: JBIDE-5394
URL: https://jira.jboss.org/jira/browse/JBIDE-5394
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Environment: EAP 5 + Riftsaw 2.0 M2 b61 + JBoss Tools
1.0.0.v200912010817N-H2-RC1
Reporter: Brad Maxwell
Assignee: Feng Qian
Attachments: InvokeHelloWSBPEL.zip
The BPEL plugin is not correctly initializing the variables.
1) Create a new Process
2) Add an Assign
3) Go to details
4) Click New
5) Select to copy from variable input/payload/inpuy
6) Select to copy to variable HelloWSPartnerLinkRequest.hello/name
7) Click away, it will prompt you to see if you want to create an Initializer
8) Click Yes
The code generate is this below. Running this process causes Riftsaw to spit out this
error: INFO [org.apache.ode.bpel.runtime.ASSIGN] (ODEServer-29) Assignment Fault:
{http://docs.oasis-open.org/wsbpel/2.0/process/executable}selectionFailure,lineNo=80,faultExplanation=No
results for expression: {OXPath10Expression name}
bpel:copy>
<bpel:from>
<bpel:literal xml:space="preserve"><tns:hello
xmlns:tns="http://jboss.com/examples/ws/Hello"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
</tns:hello>
</bpel:literal>
</bpel:from>
<bpel:to variable="HelloWSPartnerLinkRequest"
part="hello"></bpel:to>
</bpel:copy>
After days of trying various things, I then began comparing my example to the quick
starts. I found the issue is 'name' is not being initialized. I hacked the code
and added <name xmlns=""/> and it resolved the issue.
<bpel:assign validate="no" name="Assign-Input2Request">
<bpel:copy>
<bpel:from>
<bpel:literal xml:space="preserve">
<tns:hello
xmlns:tns="http://jboss.com/examples/ws/Hello"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<name xmlns=""/>
</tns:hello>
</bpel:literal>
</bpel:from>
<bpel:to part="hello"
variable="HelloWSPartnerLinkRequest"></bpel:to>
</bpel:copy>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira