[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3839) JBDS2.0.0 CR2 with Project Examples for ESB problems

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-3839:
--------------------------------------

> Just setting the runtime names won't help unless the users created the exact same names does it ? 

We could create an ESB validator (or builder) that would check for the ESB Runtime.
It would have to be run for an ESB and ordinary Java project (ESB client).

> Side-question: How come the classpath container for the runtime weren't bound even though you selected the runtime ?

I suppose the problem is that ESB projects don't have any primary facet that WTP requires. JBIDE-2887 is caused by the same issue.

> JBDS2.0.0 CR2 with Project Examples for ESB problems
> ----------------------------------------------------
>
>                 Key: JBIDE-3839
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3839
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: project-examples
>            Reporter: Stelios Koussouris
>            Assignee: Snjezana Peco
>            Priority: Minor
>
> Trying to use in JBDS 2.0.0 CR2 The "ESB Tools"
> In documentation http://download.jboss.org/jbosstools/nightly-docs/en/esb_ref_guide/html_single/index.html
> 2.3. Creating ESB Project using JBoss Tools Project Examples Wizard
> The result show on the following figure is not what I get ...
> Figure 2.7. JBoss ESB Project Examples: helloworld and helloworld_testclient
> I wanted to use my own Runtime (which exists outside the JBDS) but it automatically gives me  (as shown in the "Java Build Path")
> - JBoss ESB Runtime (jbossesb-server-4.4GA)
> - Server Library [jboss-eap-Runtime (unbound)
> - plus the version of JDK
> Now, I cannot see any way of changing the JBoss ESB Runtime it is given as 4.4 and therefore have not changed it. I have though modified the "Server Library [jboss-eap-Runtime (unbound)" to point to a SOA-P server configuration which I want my services to be deployed in. I have also removed the "jboss-eap-runtime", which is the default Target Runtime,  from my "Targeted Runtimes" instead I am pointing to the runtime that I have assigned also to "Server Library [jboss-eap-Runtime (unbound)". Now my "Java Build Path" looks like
> - JBoss ESB Runtime (jbossesb-server-4.4GA)
> - Server Library [jboss-eap-Runtime (MY ASSIGNED RUNTIME)
> - plus the version of JDK
> This has not resolved issues with imports to do so both in the helloworld and hellorworld client I used from quick fixes the "fix project setup" to import the jbossesb-rosetta.jar from a SOA-P server (not even my own one was given as an option) which has resolved now the import etc.
> I have discussed some of this with Max and suggested I raise a JIRA so here is..

-- 
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