[
https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5546:
---------------------------------
I added a new ESB category named "ESB for SOA-P 5.0", all examples in the
category are changed to work out of box with soa-p5.0, once there is a runtime point to a
soa-p5.0 and named "jboss-soa-p.5.0 Runtime" in the workspace, there will be no
compile when import the esb examples.
As suggested in JBIDE-5665, I added the examples to
http://anonsvn.jboss.org/repos/jbosstools/workspace/examples/project-exam...
for testing, once all of them works, it should be copied to
http://download.jboss.org/jbosstools/examples/project-examples-jbds30.xml
Martin, for what's the best way to import ESB examples, I suggest to create a soa-p5.0
runtime by naming it "jboss-soa-p.5.0 Runtime" before import any ESB project
examples, if so, we can avoid most of the 14 steps you mentioned above.
ESB examples packaged with JBDS 3.0 fail with SOA-P 5.0
-------------------------------------------------------
Key: JBIDE-5546
URL:
https://jira.jboss.org/jira/browse/JBIDE-5546
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.1.0.M4
Environment: JBossTools-Update-3.1.0.v200912141523M-H176-RC1.zip
or
jbdevstudio-macosx-carbon-3.0.0.v200912182118M-H46-CR1.jar
SOA-P 5.0 ER5
Reporter: Martin Malina
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: client_part.jpg, server_part.jpg
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Currently the SOA-P quickstarts store the jboss-esb.xml in the root dir of each
quickstart under jboss-as/samples/quickstarts. When you run a quickstart using the
supplied ant script, jboss-esb.xml is first moved to META-INF which is the required
location for it.
If you only try to import such a project to JBoss Tools/JBDS it won't work since it
won't look for the jboss-esb.xml in the root dir.
This is not exactly a problem of JBoss Tools as such, but I'm reporting it here for a
reference.
--
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