[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-6917) BPEL Editor does not start if extensionActivity is not defined

[Robert (Bob) Brodt (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert (Bob) Brodt resolved JBIDE-6917.
---------------------------------------

    Resolution: Done


There were a lot of things broken here. Also, the sample structured extension activity did not work because the ExtensionActivity BPEL model object did not have a container. I added a single Activity object to make this work. This means that a structured extension activity can only have one child. This probably should have been an EList<Activity> but I'm not convinced this is necessary, at least I haven't seen any of these animals in the wild.

> BPEL Editor does not start if extensionActivity is not defined
> --------------------------------------------------------------
>
>                 Key: JBIDE-6917
>                 URL: https://jira.jboss.org/browse/JBIDE-6917
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpel
>            Reporter: Robert (Bob) Brodt
>            Assignee: Robert (Bob) Brodt
>             Fix For: 3.2.x
>
>         Attachments: addpipeline.bpel
>
>
> I tried importing a BPEL source file (see attachment) that has extension activities defined, but the editor plugin did not contain serializer/deserializer classes or definitions for the extension activities. This caused an NPE during construction of the grapical EditParts.
> This is unacceptable behavior - the editor should be able to display the parts of the process that are valid and create error markers for the missing extensions.

-- 
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