[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6972) BPEL editor does not generate createInstance="yes|no" attribute for pick.

[Robert (Bob) Brodt (JIRA)]

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

Robert (Bob) Brodt commented on JBIDE-6972:
-------------------------------------------

Well...almost OK :)  I DID find that the editor does not check for this condition (from the WS-BPEL 2.0 spec):

The following example IS NOT allowed, since the <assign> activity is not a start activity:

<flow>
   <receive ... createInstance="yes" />
   <assign ... />
</flow>

The following example IS allowed, since the <assign> activity will not be performed prior to or simultaneously with the <receive> activity:

<flow>
   <links>
      <link name="RecvToAssign" />
   </links>

   <receive ... createInstance="yes">
      <sources>
         <source linkName="RecvToAssign" />
      </sources>
   </receive>

   <assign>
      <targets>
         <target linkName="RecvToAssign" />
      </targets>
      ...
   </assign>

</flow>

We should probably check for these types of conditions.

> BPEL editor does not generate createInstance="yes|no" attribute for pick.
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-6972
>                 URL: https://jira.jboss.org/browse/JBIDE-6972
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpel
>    Affects Versions: 3.2.0.M1
>            Reporter: Marek Baluch
>            Assignee: Robert (Bob) Brodt
>            Priority: Minor
>             Fix For: 3.2.0.Beta
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> The editor leaves out the createInstance="yes|no" attribute for the pick activity. This attribute must be present, especially when pick is the first activity in the process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira