Hi pfen,
Thank You for the reply.
My intention was to isolate JMS provider dependent resources from the
resource making the actual JMS connection to the provider. I wanted to avoid
clubbing both of them together. Something like putting the provider
dependent JARs and property file into a JBI-shared-lib unit & adding this
shared lib as a dependency to my SU who is actually making the connection to
the JMS provider.
This way if the end user needs to change the JMS provider in the runtime,
the only thing he needs to do is to unzip the shared-lib unit & put the
needed jars & update the property file & zip it back. Re-start the SU.
One more query:
~~~~~~~~~~
I'm using default JMS provider endpoint BC from servicemix. I can configure
request queue name in xbean.xml file as below:
------------clip---------
<jms:endpoint service="test:XYZService"
endpoint="myXYZJMSProvider" role="provider"
initialContextFactory="${java.naming.factory.initial}"
jndiProviderURL="${java.naming.provider.url}"
jndiConnectionFactoryName="${connectionFactoryName}"
jmsProviderDestinationName="${queue.TTRequestQueue}"
destinationStyle="queue" />
------------clap---------
But i also want to create a temporary response queue & receive the response
from the external JMS provider in it. Is it possible to configure the
temporary response queue in the above xbean.xml?
Thanks in advance!
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Building-a-servicemix-component-which-can-send-JMS-message-to-any-JMS-provider-tp1604221p1842275.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
