[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8409) BPEL Process editor is not associated with *.bpel files

[Robert (Bob) Brodt (JIRA)]

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

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

The BPEL Content Describer class determines whether the resource actually contains BPEL or not. It does this by looking at the root element of the XML document (it must be "process") and by the targetNamespace which must be "http://docs.oasis-open.org/wsbpel/2.0/process/executable". The filename extension is actually ignored for determining file type.

It's possible that the resource in question is an abstract process (targetNamespace="http://docs.oasis-open.org/wsbpel/2.0/process/abstract") which is not fully supported yet by the BPEL editor. See https://issues.jboss.org/browse/JBIDE-8068

> BPEL Process editor is not associated with *.bpel files
> -------------------------------------------------------
>
>                 Key: JBIDE-8409
>                 URL: https://issues.jboss.org/browse/JBIDE-8409
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpel
>    Affects Versions: 3.2.0.CR1
>            Reporter: Denis Golovin
>            Assignee: Robert (Bob) Brodt
>             Fix For: 3.2.1
>
>         Attachments: screenshot112.png, screenshot113.png
>
>
> .bpel files in resources tree look like text files. There is no bpel icon associated with file.
> !screenshot112.png!
> Editor opened using workaround has no icon as well.
> !screenshot113.png!

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