Solved my problem by using the following snapshot at camel website...
initially i was trying at router level ..then i moved to component level
which seems logical.
Register component with camel context and then start the router.
A workaround is to use a custom DestinationResolver:
JmsComponent wmq = new JmsComponent(connectionFactory);
wmq.setDestinationResolver(new DestinationResolver(){
public Destination resolveDestinationName(Session session, String
destinationName, boolean pubSubDomain) throws JMSException {
MQQueueSession wmqSession = (MQQueueSession) session;
return wmqSession.createQueue("queue:///" + destinationName +
"?targetClient=1"); }
});
*Shashi Kant *
***"Think positive and find fuel in failure"*
*+917259733668
*
http://thinkndoawesome.blogspot.com/
*System/Software Engineer*
*Hewlett-Packard India Software Operations.
*
On Tue, Jun 4, 2013 at 4:09 PM, shashi kant <[email protected]> wrote:
> Not a advanced user .. i have seen that link before.
>
> can't figure out how do just that from camel.
>
> If u can just give some idea regarding that
>
>
> *Shashi Kant *
> ***"Think positive and find fuel in failure"*
> *+917259733668
> *
> http://thinkndoawesome.blogspot.com/
> *System/Software Engineer*
> *Hewlett-Packard India Software Operations.
> *
>
>
> On Tue, Jun 4, 2013 at 2:55 PM, David J. M. Karlsen [via Camel] <
> [email protected]> wrote:
>
>> Does this help?
>>
>> http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.doc%2Fmi21980_.htm
>>
>>
>> 2013/6/3 shashi.kant <[hidden
>> email]<http://user/SendEmail.jtp?type=node&node=5733784&i=0>>
>>
>>
>> > I have been trying to send message to a IBM websphere MQ queue which
>> has to
>> > be in IBM500 charset, MQFMT_STRING format and encoding 273 from a Camel
>> > 2.10.4 application running on jboss. tried General ways of setting the
>> > connectionfactory properly with following values:
>> > connection.setTransportType(JMSC.MQJMS_CLIENT_NONJMS_MQ);
>> > connection.setStringProperty(WMQConstants.JMS_IBM_CHARACTER_SET,
>> "500");
>> > connection.setStringProperty(WMQConstants.JMS_IBM_FORMAT,
>> > MQC.MQFMT_STRING);
>> > connection.setIntProperty(WMQConstants.JMS_IBM_ENCODING, 273);
>> > connection.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE,
>> > WMQConstants.WMQ_CLIENT_NONJMS_MQ); I have tried
>> > IBMWebSphereMqDestinationResolver
>> >
>> >
>> https://jira.springsource.org/secure/attachment/12688/IBMWebSphereMqDestinationResolver.java
>> > But everytime at the Websphere MQ end MQRFH2 header is there. I can't
>> > figure
>> > out any solution to this problem.. Somebody please help me out.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725.html
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>> >
>>
>>
>>
>> --
>> --
>> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the
>> discussion below:
>>
>> http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725p5733784.html
>> To unsubscribe from Camel always sending MQRFH2 headers to target
>> WebsphereMQ queue., click
>> here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5733725&code=c2hhc2hpc2tpbGxzQGdtYWlsLmNvbXw1NzMzNzI1fC0xNDMxMTY0MTkx>
>> .
>> NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725p5734007.html
Sent from the Camel - Users mailing list archive at Nabble.com.
