[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5546) ESB examples packaged with JBDS 3.0 fail with SOA-P 5.0

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-5546:
--------------------------------------

Workaround from Brian:
For example, to run the Project Example - JBoss ESB HelloWorld Example, I follow these simple steps in a new JBT workspace:

1) In the tooling, create a new server instance for your SOA-P 5.0 runtime in the Servers view (I've been using the EAP 5.0 version and just renaming it SOA-P 5). 

2) In the tooling, go to Help->Project Examples. Select the ESB -> JBoss ESB HelloWorld Example - ESB. Click Finish.

3) In the Quick Fix dialog, select the "Unbound classpath container: JRE System Library [java-1.6.0-openjdk-..." item. Click "Quick Fix".

4) Select "Replace with other library". In the "Add Library" dialog, select JRE System Library and step through selecting a different JRE (such as Sun's JRE jdk1.6.0_14). Click Finish. 

5) Now you see additional things to fix. Select "Target runtime jboss-soa-p.4.3.0 Runtime is not defined.". Click Quick Fix. 

6) Select Configure Target Runtimes. In the Targeted Runtimes property page, select your SOA-P 5.0 runtime server. Click OK.

7) Select any of the "The import x cannot be resolved" messages and click Quick Fix.

8) Select "Fix project setup..." and click Finish.

9) You should see a "Project Setup Fixes" dialog come up with a message - "No proposals have been found..." In the message is a "Click here to manually configure the build path..." Click the hyperlink.

10) Now you're in the Build path properties for the project. Select the "Libraries" tab. CLick on the "JBoss ESB Runtime" library and select "Edit..."

11) You should see the Edit Library dialog come up with "Select a ESB runtime to add to the project classpath" - select the one associated with the SOA-P 5 runtime server. Click Finish.

12) Back in the Build path properties, now select "Server Library" and click "Edit..."

13) You should see another Edit Library dialog. Select your SOA P 5.0 runtime server. Click Finish.

14) Click OK on the Build path properties dialog. You should come back to the Quick Fix dialog with no markers. Click Finish.


> 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
>         Attachments: client_part.jpg, server_part.jpg
>
>
> 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