[
https://jira.jboss.org/browse/JBIDE-7786?page=com.atlassian.jira.plugin.s...
]
Rob Stryker resolved JBIDE-7786.
--------------------------------
Assignee: Rob Stryker (was: Robert (Bob) Brodt)
Resolution: Done
Associating a bpel project with a runtime accomplishes very little, specifically because
bpel projects do not have java classes. Without java classes, adding a runtime provides
very little value. However, I will commit the patch so that you can associate the runtime
;)
Using the "Add / Remove from server" dialog, you can still add BPEL projects to
the proper server, however the "Run On Server..." action is *NOT* currently
enabled for bpel projects. The reason it is not enabled is because, for web projects, we
know what URL to travel to when you run the project on the server. For a .jsp file we also
know where to go.
Nobody has instructed me what a "Run On Server" action should do for a bpel
project or any specific files within a bpel project. What I'm looking for here is some
action to take if a user wants to "run" a .wsdl file on the server. Should it
open a web browser? to what URL? Etc etc.
So... action specifications for the run-on-server action for both bpel projects and
specific files within bpel would be of much assistance to me if you want the run on server
action to be enabled. However, this JIRA is not about that, and so if this is an issue for
your team I encourage you to open another JIRA task and assign it to me and include all
such relevant information.
For now, I've fixed the facet error related to this bug ;) Enjoy!
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: Rob Stryker
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