[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI

[Brian Fitzpatrick (JIRA)]

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

Brian Fitzpatrick commented on JBIDE-5038:
------------------------------------------

To get the editor:

1) Create a file called "bpel-deploy.xml" in the same directory with the *.bpel and *.wsdl files. OR Create a new Apache ODE Deployment Descriptor using the New Apache ODE Deployment Descriptor wizard. OR try copy an existing bpel-deploy.xml file (like from the imported BPEL quickstarts) 

2) Try to open the file. 

By default, the ODE Deployment Descriptor editor tries to open the file, and fails with the exception above.

The only workaround is to open the .xml file in a different editor such as the XML Editor or the Text Editor. 

> With changes to BPEL project wizard, BPEL deployment is broken in UI
> --------------------------------------------------------------------
>
>                 Key: JBIDE-5038
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5038
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpm
>            Reporter: Brian Fitzpatrick
>            Assignee: Denny Xu
>            Priority: Critical
>             Fix For: 3.1.0.CR1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Rob helped out with getting the BPEL project structure working like the ESB project structure so we are more consistent down the line and have more flexibility. We now have a JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
> The downside to this is that we lose the Apache ODE Descriptor code that used to work (in fact, it's broken and throws an error when you try to use it or open a non-ODE deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in: org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's now not connected to our BPEL project. So we need to create a new mechanism for generating the JBoss Riftsaw deployment descriptor.

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