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

[Jeff DeLong (JIRA)]

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

Jeff DeLong commented on JBIDE-3651:
------------------------------------

I found another jar conflict; this time with the scout jar. The JbossAS client libraries contain scout.jar, while the esb libraries contain scout-1.0rc2.aop.jar. If scout jar is picked up first in the runtime classpath of the client, it results in an exception using the following property from jbossesb.properties:

    	<property name="org.jboss.soa.esb.registry.queryManagerURI"     		
    		value="jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire"/>    		

It appears the scout.jar does not understand jnp.
I think having all these jars on the classpath is a bad idea. They clearly are not all needed, and some of them have conflicts between what is in 
jboss-soa-p.4.3.0/jboss-as/server/default/deploy/jbossesb.sar/lib and jboss-soa-p.4.3.0/jboss-as/client


> 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