[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=12450962#action_12450962 ] 

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

I did some changes for this and other issues. Now we can support a jboss server that must support esb.(for example: jbossesb-server-4.4GA, jboss-as server from SOA-P)

After you import these examples into your workspace, maybe some issues. But don't worry, you only need to do some steps to fix them:
1 set your jboss server and jboss esb runtime and remember the esb runtime name. The server must support esb.
2 right-click on the project, and select the properties action.
3 In the opened wizard, choose Java Build Path, then click Libraries Tab, then you can correct the jboss server and jboss esb runtime in the opened page. 
4 rebuild the project, I believe you will get a correct project.

Except said as above, you need not do anything.

So, jeff, you must not add any jars to your classpath by yourself. Please test again, if any question, please let me know

> 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