[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6268) Hello world example client fails sending ESB message

[Brian Fitzpatrick (JIRA)]

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

Brian Fitzpatrick commented on JBIDE-6268:
------------------------------------------

Hi Libor...

So what I recall for this one is that there's a classpath issue with running the SendESBMessage class that prevents us from running it in the tooling. I ran into this when I was trying to develop an ESB tester for the tooling. 

However, you can run it from the command line if you have ant installed...

In the SOA-P samples directory... [runtime/jboss-as/samples/quickstarts/helloworld directory

1) "ant deploy" deploys the sample on the runtime
2) "ant runtest" runs the SendJMSMessage class
3) "ant sendesb" runs the SendESBMessage class
4) "ant undeploy" undeploys the sample from the runtime

You should see in the console the results of a SendJMSMessage and SendESBMessage are different. 

> Hello world example client fails sending ESB message
> ----------------------------------------------------
>
>                 Key: JBIDE-6268
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6268
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb, project-examples
>    Affects Versions: 3.2.next
>         Environment: jboss eap 5.0 GA, esb 4.7
>            Reporter: Libor Zoubek
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.2.next
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I am playing with HelloWorld and HelloWorld ESB examples. I've successfully deployed HelloWorld, I am able to run SendJMSMessage client class with results as expected, but SendEsbMessage fails
> Here is result:
> Usage SendEsbMessage <category> <name> <text to send>
> Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: org.apache.ws.scout.transport.TransportException: javax.naming.NameNotFoundException: InquiryService not bound
> 	at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:545)
> 	at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:174)
> 	at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:155)
> 	at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:197)
> 	at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:56)
> Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: javax.naming.NameNotFoundException: InquiryService not bound
> 	at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:348)
> 	at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.findEPRs(InVMRegistryInterceptor.java:85)
> 	at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.findEPRs(RegistryFactory.java:229)
> 	at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226)
> 	at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:532)
> 	... 4 more
> Caused by: javax.xml.registry.JAXRException: org.apache.ws.scout.transport.TransportException: javax.naming.NameNotFoundException: InquiryService not bound
> 	at org.apache.ws.scout.registry.BusinessQueryManagerImpl.findConcepts(BusinessQueryManagerImpl.java:544)
> 	at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.getJBossESBTModel(JAXRRegistryImpl.java:653)
> 	at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:307)
> 	... 8 more

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