Created
March 31, 2011 09:11
-
-
Save albuquerquev/896077 to your computer and use it in GitHub Desktop.
Connecting To WebSphere MQ Using Spring JMS And Maven Post - Spring Configuration (http://goo.gl/KQ2rh)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<!-- WebSphere MQ Connection Factory --> | |
<bean id="mqConnectionFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory"> | |
<property name="hostName"> | |
<value>${queue_hostname}</value> | |
</property> | |
<property name="port"> | |
<value>${queue_port}</value> | |
</property> | |
<property name="queueManager"> | |
<value>${queue_manager}</value> | |
</property> | |
<property name="transportType"> | |
<value>1</value> | |
</property> | |
</bean> | |
<!-- JMS Queue Connection Factory --> | |
<bean id="jmsQueueConnectionFactory" | |
class="org.springframework.jms.connection.SingleConnectionFactory102"> | |
<property name="targetConnectionFactory"> | |
<ref bean="mqConnectionFactory" /> | |
</property> | |
<property name="pubSubDomain"> | |
<value>false</value> | |
</property> | |
</bean> | |
<!-- JMS Destination Resolver --> | |
<bean id="jmsDestinationResolver" | |
class="org.springframework.jms.support.destination.DynamicDestinationResolver"> | |
</bean> | |
<!-- JMS Queue Template --> | |
<bean id="jmsQueueTemplate" class="org.springframework.jms.core.JmsTemplate102"> | |
<property name="connectionFactory"> | |
<ref bean="jmsQueueConnectionFactory" /> | |
</property> | |
<property name="destinationResolver"> | |
<ref bean="jmsDestinationResolver" /> | |
</property> | |
<property name="pubSubDomain"> | |
<value>false</value> | |
</property> | |
<property name="receiveTimeout"> | |
<value>20000</value> | |
</property> | |
</bean> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!. I configured my project like this, but I need an JNDI approach. Did you configured in that way? thanks