[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5038:
---------------------------------
This issue is because that the classes of the plugin
"org.eclipse.bpel.apache.ode.deploy.model" are missing, I am not sure why Jboss
tools build did not pick the classes file of the plugin. When I run BPEL tools from
code, the descriptor editor works.
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