[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5394) BPEL Plugin is not correctly initalizing variables

[Brad Maxwell (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12501594#action_12501594 ] 

Brad Maxwell commented on JBIDE-5394:
-------------------------------------

Yes,   <tns:result></tns:result> format is ok with me.

I was looking at some wsdl and I see what you mean.  It looks like the wsdls that have messages defined as an element seem to always set minOccurs="0", which means that it is valid to have none specified.  So the issue is after you initialize the variable, if the user tries to map a variable or expression to the the initialized element, then it will fail at runtime because it tries to copy to an undefined location.

So there are a couple of ways it could be handled:
1) If they choose to initialize the variable, then it could create an element for everything including ones that have minOccurs="0" and that should take care of the issue.

2)  If they chose to initialize the variable, then do as it does now, but then if they try to map something inside of the element that hasn't been initialized, then it could be created then.

I think #1 would be the easiest to do.

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
>             Fix For: 3.1.0.CR2
>
>         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