[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8068) BPEL Editor has problems dealing with abstract processes

[Robert (Bob) Brodt (JIRA)]

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

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

This is a more complicated issue and will require some time to fix & test properly. For now I have updated the Content Describer to check for the "abstract" namespace, and also added a warning dialog if an Opaque activity is dropped on the designer canvas - this changes the process to "abstract".

The rest of this will have to wait until 3.3

> BPEL Editor has problems dealing with abstract processes
> --------------------------------------------------------
>
>                 Key: JBIDE-8068
>                 URL: https://issues.jboss.org/browse/JBIDE-8068
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpel
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Robert (Bob) Brodt
>            Assignee: Robert (Bob) Brodt
>            Priority: Minor
>             Fix For: 3.2.1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> For abstract processes, the namespace is "http://docs.oasis-open.org/wsbpel/2.0/process/abstract" but much of the editor code simply assumes that the namespace is always "http://docs.oasis-open.org/wsbpel/2.0/process/executable". This causes all kinds of problems when doing lookup of namespace prefixes to identify BEPL "built-in" features (e.g. fault names). This is also the reason why the BPELContentDescriber does not recognize an abstract process as a BPEL file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira