This content has been marked as final.
Show 4 replies
-
1. Re: EJB endpoint for the ESB
beve Sep 10, 2008 3:00 AM (in response to lisa_rossi)Hi,
Is there any example of creating an EJB endpoint for the Service Bus?
The following quickstart demonstrates an action that calls out to en EJB:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/ejbprocessor/
Is this sort of what you were looking for?
Regards,
/Daniel -
2. Re: EJB endpoint for the ESB
freejohn22 Dec 3, 2008 4:16 AM (in response to lisa_rossi)Hello !
I also am looking for an example of EJB endpoint.
I have downloaded the example from the link provided, however if I try launch the build.xml I get the error:C:\jbossesb-server-4.4.GA\samples\quickstarts\conf\base-build.xml:518: **** DEPLOYMENT FAILED... Sorry, this Quickstart requires a JBoss EJB3 container. 'C:\jbossesb-server-4.4.GA' does not have an EJB3 container. Check the 'org.jboss.esb.server.home' property in ./quickstarts.properties"
however if I set this property to :<property name="org.jboss.esb.server.home" value="C:\jboss-4.2.0.GA"/>
then I get the error that esb classes are missing......
So my doubt is:
1) should I patch JBoss ESB adding the EJB3 container (and deploy the EJB there )?
2) or should I deploy the EJB to JBoss and so I need to start up 2 JBoss: JBoss standard (EJB3) and JBoss ESB ?
thanks a lot
john -
3. Re: EJB endpoint for the ESB
beve Dec 3, 2008 4:34 AM (in response to lisa_rossi)1) should I patch JBoss ESB adding the EJB3 container (and deploy the EJB there )?
2) or should I deploy the EJB to JBoss and so I need to start up 2 JBoss: JBoss standard (EJB3) and JBoss ESB ?
Either way is fine. I think the easiest would be to deploy the ESB to a JBossAS installation that has support for EJB3. That way you only have one server. But this depends on you requirements. If you just want to try this out then that might be the fastest way.
Regards,
/Daniel -
4. Re: EJB endpoint for the ESB
freejohn22 Dec 11, 2008 6:22 AM (in response to lisa_rossi)Hello,
sorry to bother again. I have tried adding the EJb Processor action to my Action pipeline:<action name="EJBTestVoid" class="org.jboss.soa.esb.actions.EJBProcessor"> <property name="ejb3" value="true" /> <property name="method" value="printMessage" /> <property name="jndi-name" value="SimpleSLSB/remote" /> <property name="initial-context-factory" value="org.jnp.interfaces.NamingContextFactory" /> <property name="provider-url" value="192.168.10.1:1099" /> <property name="ejb-params"> <arg0 type="java.lang.String">org.jboss.soa.esb.message.defaultEntry</arg0> </property> </action>
however I get an "Error configuring action processing pipeline"12:09:45,078 WARN [ServiceController] Problem starting service jboss.esb:deploy ment=helloworld.esb org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise ... 52 more 12:09:45,171 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb:deployment=helloworld.esb State: FAILED Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline I Depend On: jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_esb jboss.esb:deployment=jbossesb.esb jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_gw --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb:deployment=helloworld.esb State: FAILED Reason: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline I Depend On: jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_esb jboss.esb:deployment=jbossesb.esb jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_gw
I didn't add anything else besides the "action"..what could be the problem ?
thanks a lot
john