It took us a while too let things sink in and too grasp the problem
correctly. We have been approaching the problem in the wrong way not
understanding camel.

This problem has nothing too do with camel. However it would be very nice to
be able to set a URI as in the case with servicemix-jms where we could
simply type into the destinationName:

<jms:provider service="esb:IBMMQOutbound"
endpoint="mqOutbound"
destinationName="queue:///MyQueueOutBound?targetClient=1"
connectionFactory="#mqConnectionFactory"/>      
        
<bean id="mqConnectionFactory"
class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType">
<util:constant static-field="com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ"/> 
</property>
<property name="queueManager" value="QMgr"/>
<property name="hostName" value="xxx.xxx.xxx.xxx"/>     
<property name="port" value="1414"/>
</bean>

Something like this would be ideal in our case:

<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring";>
<route>
<from uri="activemq:myqueueinbound"/>
<to uri="ibmmq:queue:///MyQueueOutBound?targetClient=1"/>
</route>
</camelContext>


However this is not the case. We believe that something like this should
solve the problem if we only figured out the correct spring configuration:

<bean id="ibmmq" class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory">
<bean class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType">
<util:constant static-field="com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ"/>
</property>
<property name="queueManager" value="QMgr"/>
<property name="hostName" value="xxx.xxx.xxx.xxx"/>    
<property name="port" value="1414"/>
</bean>
</property>
<property name="queue" ref="ibmqueueprop">
</bean>

<bean id="ibmqueueprop" class=" com.ibm.mq.jms.MQDestination">
<property name="targetClient" value="1"/>    
</bean>


If someone finds a solution to this problem please send us a message or post
it here. 
Thanks again Claus for your assistance in this matter!
We will keep this update if we stumble on the solution =)


-- 
View this message in context: 
http://www.nabble.com/Bridging-the-ActiveMQ-with-IBM-Websphere-using-Camel-tp19623329s22882p19833105.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to