[jeffdelong]

I got the Helloworld quickstart to work on JBoss-4.0.5.GA with JBoss Messaging 1.0.1.SP2 and Oracle 10G. I had to:

1) change esb-quickstart-service.xml to use JBoss Messaging Queue definitions
2) copy jbossesb-properties to /conf
3) fix Oracle schema - change address_line.line to allow nulls
and change binding_template.access_point_url from 255 to 2048
4) put jboss-remoting.jar from jboss-messsaging.sar, jboss-messaging-client.jar, and jboss-aop-jdk50.jar into the JMS client classpath
5) put jboss-messaging-client.jar in server/../lib
6) copy Quickstart_helloworld.jar into jbossesb.sar (is the correct way to deploy "custom" ListenerActions?)
7) update the jbossesb-listener and jbossesb-gateway files to include the helloworld gateway and listener definitions (this was described in the QuickStart.pdf).

[jeffdelong]

I got Trailblazer2 mostly working in the same environment (plus one other addition - I replace the default Jboss transaction manager with JBoss Transactions).

One issue I found with the Trailblazer is with the ManagerJMS. It was looking up "UILConnectionFactory". I changed it to "ConnectionFactory", which should be portable between JBoss Messaging and JBossMQ.

I also found a minor nit on the build script. The following did not work for me, as there is no build directory under jbossesb.

 <property name="org.jboss.soa.esb.lib.dir" value="${org.jboss.soa.samples.trailblazer.esb_home}/build/jbossesb/lib"/>

So I removed the build/jbossesb and it used the lib directory under the trailblazer directory.

Another questions: where should quote.st be deployed? It is not being found when attempting to send the email.

This is all with RC1.

Thanks

[daniel.brum]

Jeff, can you test this with the version in trunk? Would appreciate your feedback.

quotes.st should be in a tb/quotes folder.

[jeffdelong]

Yes, I will check out latest from trunk this afternoon and test it out.

[jeffdelong]

I built jbossesb from trunk and deployed sar to jboss-4.0.5.GA along with esb configuration files and war. I am getting an exception when I start the server

org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] Cannot launch <org.jboss.soa.esb.listeners.message.MessageAwareListener>

java.lang.NoSuchMethodException: org.jboss.soa.esb.listeners.message.MessageAwareListener.(org.jboss.soa.esb.listeners.message.EsbListenerController, org.jboss.soa.esb.helpers.ConfigTree)
at java.lang.Class.getConstructor0(Class.java:2647)
at java.lang.Class.getConstructor(Class.java:1629)
at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.tryToLaunchChildListener(EsbListenerControllerFactory.java:394)
at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.run(EsbListenerControllerFactory.java:346)
at java.lang.Thread.run(Thread.java:595)
2007-01-02 11:04:25,640 ERROR [org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] Cannot launch <org.jboss.soa.esb.listeners.message.MessageAwareListener>

java.lang.NoSuchMethodException: org.jboss.soa.esb.listeners.message.MessageAwareListener.(org.jboss.soa.esb.listeners.message.EsbListenerController, org.jboss.soa.esb.helpers.ConfigTree)
at java.lang.Class.getConstructor0(Class.java:2647)
at java.lang.Class.getConstructor(Class.java:1629)
at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.tryToLaunchChildListener(EsbListenerControllerFactory.java:394)
at org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl.run(EsbListenerControllerFactory.java:346)
at java.lang.Thread.run(Thread.java:595)
2007-01-02 11:04:25,656 DEBUG [org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] About to sleep 49969
2007-01-02 11:04:25,734 INFO [org.jboss.soa.esb.listeners.State] Listener component [org.jboss.soa.esb.listeners.message.EsbListenerControllerFactory$EsbListenerControllerImpl] is now in a state of 'Ready'.
2007-01-02 11:04:25,734 DEBUG [org.jboss.soa.esb.listeners.message.EsbListenerControllerService] Started jboss.org:service=EsbListenerController
2007-01-02 11:04:25,734 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.org:service=EsbListenerController dependent components: []
2007-01-02 11:04:25,734 DEBUG [org.jboss.system.ServiceController] starting service jboss.org:service=GatewayListenerController
2007-01-02 11:04:25,734 DEBUG [org.jboss.soa.esb.listeners.gateway.GatewayListenerControllerService] Starting jboss.org:service=GatewayListenerController
2007-01-02 11:04:25,734 INFO [org.jboss.soa.esb.listeners.gateway.GatewayListenerControllerService] starting message aware listener with config file jbossesb-gateway.xml
2007-01-02 11:04:25,734 INFO [org.jboss.soa.esb.listeners.gateway.GatewayListenerController] No value specified for: endTime - Listener will run until parent container/process terminates.
2007-01-02 11:04:25,750 DEBUG [org.jboss.soa.esb.listeners.gateway.GatewayListenerControllerService] Started jboss.org:service=GatewayListenerController
2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.org:service=GatewayListenerController dependent components: []
2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] starting service jboss.jca:service=DataSourceBinding,name=JBossESBDS
2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss.jca:service=DataSourceBinding,name=JBossESBDS
2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] starting service jboss.jdbc:service=metadata,datasource=JBossESBDS
2007-01-02 11:04:25,750 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.DataSourceMetaData] Starting jboss.jdbc:service=metadata,datasource=JBossESBDS
2007-01-02 11:04:25,750 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.DataSourceMetaData] Started jboss.jdbc:service=metadata,datasource=JBossESBDS
2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.jdbc:service=metadata,datasource=JBossESBDS dependent components: []
2007-01-02 11:04:25,750 DEBUG [org.jboss.system.ServiceController] starting




Also getting:

2007-01-02 11:04:34,750 INFO [org.apache.juddi.registry.local.Registry] Loading jUDDI configuration.
2007-01-02 11:04:34,750 INFO [org.apache.juddi.registry.local.Registry] Resources loaded from: /C:/jboss-ps-0.1/jboss-4.0.5.GA/server/ps/conf/juddi.properties
2007-01-02 11:04:34,750 INFO [org.apache.juddi.registry.local.Registry] Initializing jUDDI components.
2007-01-02 11:04:34,750 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Service name: trailblazer-jmsbank:jmsbankreplies
2007-01-02 11:04:34,750 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Description: null
2007-01-02 11:04:34,750 INFO [org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl] Key id: 8A386AE0-909D-11DB-AAE0-C8137B127B1B
2007-01-02 11:04:34,781 ERROR [STDERR] Exception in thread "Thread-36"
2007-01-02 11:04:34,781 ERROR [STDERR] java.lang.LinkageError: loader constraints violated when linking org/w3c/dom/Document class
2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.internal.soa.esb.addressing.helpers.EPRHelper.toXMLString(EPRHelper.java:151)
2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:185)
2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController.register(GatewayListenerController.java:644)
2007-01-02 11:04:34,781 ERROR [STDERR] at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.run(JmsGatewayListener.java:75)
2007-01-02 11:04:34,781 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)

[jeffdelong]

I removed xml-apis-1.3.02.jar and xercesImpl-2.7.1 from the jbossesb.sar and the second exception appears to have gone away. There are versions of these jars in jboss-4.0.5/lib/endorsed (xalan.jar is in lib and the sar as ell).

[jeffdelong]

As for the first exception, it appears that

MessageAwareListerner extends AbstractManagedListener and the constructor takes a org.jboss.soa.esb.listener.ListenerManager as an argument. However, from the stack trace it appears that a org.jboss.soa.esb.listener.message.ESBListenerController is being passed, which does not implement ListenerManager.

So the messageAwareListener.getContructor(org.jboss.soa.esb.listener.ListenerManager, org.jboss.soa.esb.helper.ConfigTree) is failing.

Not clear to me the relationship between the two interfaces: ListenerManager and ESBListenerController

[tommy111]

hi
any know that how jbossESB reply message to client?

[marklittle]

Probably best to create a new forum entry in the User Forum, rather than hijacking an old Design Forum posting.