This content has been marked as final.
Show 2 replies
-
1. Re: Talking to JBossMQ from 3rd party Application server usi
narayanrm Feb 2, 2005 1:00 PM (in response to narayanrm)
I think the probable solution lies here in the deployed rar getting the context and looking up for the JBoss JMS provider. In case of the Jboss App server this is done by JNDI Provider Adapter given as in the ds.xml<mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"> <attribute name="ProviderName">DefaultJMSProvider</attribute> <attribute name="ProviderAdapterClass"> org.jboss.jms.jndi.JNDIProviderAdapter </attribute> <!-- The combined connection factory --> <attribute name="FactoryRef">XAConnectionFactory</attribute> <!-- The queue connection factory --> <attribute name="QueueFactoryRef">XAConnectionFactory</attribute> <!-- The topic factory --> <attribute name="TopicFactoryRef">XAConnectionFactory</attribute> <!-- Access JMS via HAJNDI --> <attribute name="Properties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=localhost:1100 </attribute> </mbean>
If I am correct, how could the same be done in the 3rd party Application Servers?
Does the rar gets the context from the MBean by any chance? -
2. Re: Talking to JBossMQ from 3rd party Application server usi
adrian.brock Feb 3, 2005 1:06 AM (in response to narayanrm)This is an FAQ:
http://www.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnMDBToTalkToARemoteQueue
You are configuring the jndi context properties and bindings in the JMSProvider.
These need not be referencing a JBoss/JBossMQ instance/cluster.