[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3651) Runtime classpath on ESB Client example results in exception

[Feng Qian (JIRA)]

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

Feng Qian commented on JBIDE-3651:
----------------------------------

to Jeff,
Sorry, you need not to use the nightly build of jboss tools, you only need to import the example again. And do the steps as above.
to Max,
When all apps run on the server, they will find the class in the web-inf's lib folder at first, secondly is the server lib. But when the apps in our tools, these jars are all in the project's classpath, so maybe have some conflict. As jboss ws module, when we  will generate jboss ws client, we need to remove two jars from the project classpath. But for this issue, I think we need not to care this problem because now the example can run and we need not to add any jar by ourself. 

> Runtime classpath on ESB Client example results in exception
> ------------------------------------------------------------
>
>                 Key: JBIDE-3651
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3651
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.0.0.cr1
>         Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar, RHEL 5, JDK 1.5.0.11, SOA-P 4.3 (soa-4.2.0.GA).
>            Reporter: Jeff DeLong
>            Assignee: Feng Qian
>             Fix For: 3.0.0.GA
>
>
> Problem occurs when running helloworld_testclient. The following exception occurs:
> Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [  ]] to Service [JBossESB-Internal:DeadLetterService].  Check for errors.
> I can get the exception to go away and the client to run successfully if I add jbossall-client to the FRONT of the Eclipse client application Run Configuration classpath. jbossall-client is already included JBoss 4.2 Runtime. However JBoss ESB Runtime is before JBoss 4.2 Runtime in the Run Configuration classpath, so I guess there is some class in one of the JBoss ESB Runtime jars that is an issue (my JBoss ESB Runtime is from SOA-P 4.3).
> Not sure how to change the order of the libraries. The Run Configuration classpath uses the project default classpath, however the libraries, etc. are listed in the reverse order of how they are listed in the Properties - > Java Build Path -> Libraries, which appears to have libraries listed in alphabetical order, so JBoss 4.2 Runtime is before JBoss ESB Runtime. Hence they are reversed in the Run Configuration classpath.

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