[
https://jira.jboss.org/browse/JBIDE-7786?page=com.atlassian.jira.plugin.s...
]
Robert (Bob) Brodt commented on JBIDE-7786:
-------------------------------------------
Just because JBoss shows up as a selectable runtime, doesn't mean that it will
actually be able to execute a BPEL process. This depends on whether or not Riftsaw has
been installed. I think we should probably (for JBDS CR1?) do something along the lines of
what Apache have done with Tomcat/ODE: you must associate an ODE runtime with the BPEL
project - you can't simply deploy to a Tomcat instance. So, what I think we should do
is create a Riftsaw runtime plugin, which will expose the BPEL facet ID, and then have the
plugin check to ensure that Riftsaw has been installed. Riftsaw installation (if required)
could possibly be done as part of the runtime instance creation in the Eclipse IDE. We
should then revert Rob's change to the AS core plugin (i.e. remove
jbt.bpel.facet.core)
Unable to associate BPEL project with SOA 5.1 runtime.
------------------------------------------------------
Key: JBIDE-7786
URL:
https://jira.jboss.org/browse/JBIDE-7786
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.1.2
Reporter: Marek Baluch
Assignee: Robert (Bob) Brodt
Fix For: 3.2.0.CR1
Attachments: greyed-out.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
It's not possible to associate a BPEL project with a SOA 5.1 runtime. Even if
there's a usable runtime then it's greyed-out. This association should be done
automatically on project creation. According to the "targeted runtimes" dialog
there seem to be facets blocking it. There are following facets associated with the
project:
BPEL 2.0 Facet (checked)
Contexts and Dependency Injection (not checked)
Java (not checked)
JavaScript (not checked)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira