Re: MQ Series and RFH2 Heading

Hello,

I'm facing the same problem: sending a Websphere MQ JMS messages  to a non
jms client.

My workaround was to make a vendor specific JmsConnector. I subclassed
JmsConnector and I overrode the method doConnect as follows.

        public void doConnect() throws ConnectException {
                super.doConnect();
                this.setJmsSupport( new WebSphereMQSupport(this, this.getJndiContext(),
false,
                   false));
        }

Second I implemented WebSphereMQSupport which is a subclass Jms102bSupport
(in my case, but it could be as well Jms11Support). I overrode the method
createDestination as follows.

        public Destination createDestination(Session session, String name,
                        boolean topic) throws JMSException {
                Destination destination = super.createDestination(session, name, topic);
                ((MQDestination) destination)
                                .setTargetClient( JMSC.MQJMS_CLIENT_NONJMS_MQ);

                return destination;
        }


Andrew Perepelytsya wrote:

>
> Eric,
>
> The real solution I'd like to implement one day is to provide
> vendor-specific JMS connectors, defaulting to vendor-specific support
> classes and properties. Yeah, it's not that all compatible in the real
> world.
>
> The only factor slowing down it's implementation is it has to use
> reflection, and then cache the class instantiation results for performance
> reasons, thus a little bit more involved than just some properties
> defaults.
>
> Andrew
>
> On 11/30/06, Biva < eric.biva@...> wrote:
>>
>>
>> Hello
>> I tried and ... it works ;o)
>> So this is THE solution to specify that your message is sent to a non-JMS
>> receiver (WebSphere MQ in my case).
>>
>> Best regards
>> Eric
>>
>>
>> Biva wrote:
>> >
>> > Hi Andrew
>> > not yet, I was wondering if, one year later, a real solution was found.
>> > But it seems that it is not the case... unfortunately.
>> > I will try the Yvette's workaround.
>> >
>> > Regards
>> > Eric
>> >
>> >
>> > Andrew Perepelytsya wrote:
>> >>
>> >> Eric,
>> >>
>> >> Have you tried the workaround Yvette had posted? It worked for him.
>> >>
>> >> Andrew
>> >>
>> >> On 11/29/06, Biva <eric.biva@...> wrote:
>> >>>
>> >>>
>> >>> Hello
>> >>> one year after, I'm facing the same problem.... :-(
>> >>> Can anyone help me to get rid of this RFH2 header?
>> >>>
>> >>> Thank you
>> >>> Eric
>> >>>
>> >>>
>> >>> YQuinby wrote:
>> >>> >
>> >>> > Hi,
>> >>> >
>> >>> > We are using Mule to send JMS messages via IBM MQ Series.
>> >>> >
>> >>> > I have the messages arriving on the queues, but we need to remove
>> the
>> >>> JMS
>> >>> > RFH2 header from our messages.
>> >>> >
>> >>> > According to IBM documentation, this can be done by appending
>> >>> > targetClient=1 to the end of a URI.
>> >>> >

>> >>> > eg.
>> >>> >
>> >>> > jms://QUEUE_MANAGER/QUEUE_NAME?targetClient=1
>> >>> >
>> >>> > where 1=MQ and 0=JMS
>> >>> >

>> >>> > However, this doesn't seem to be working for us.
>> >>> >
>> >>> > Has anyone else who uses IBM MQ Series come across this issue
>> before?
>> >>> >
>> >>> > Thanks.
>> >>> >
>> >>> > ===================================================
>> >>> > HBF Health Funds Inc. a registered organisation under the National
>> >>> Health
>> >>> > Act
>> >>> > HBF Insurance Pty Ltd ACN  009 268 277
>> >>> > This email is a confidential communication intended only for the
>> named
>> >>> > Addressee(s).
>> >>> > If you are not that person any disclosure, copying, distribution or
>> >>> use
>> >>> of

>> >>> > this email

>> >>> > or the information in it is prohibited. Please notify us
>> immediately
>> >>> by
>> >>> > telephone, (+61) 08 9265 6111 or return email and delete this
>> email.
>> >>> > The views in this email may be personal to the author and not those
>> of
>> >>> > HBF.
>> >>> >
>> >>> >
>> >>>
>> >>> --
>> >>> View this message in context:
>> >>>
>> http://www.nabble.com/-mule-user--MQ-Series-and-RFH2-Heading-tf567815.html#a7603318
>> >>> Sent from the Mule - User mailing list archive at Nabble.com.
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe from this list please visit:
>> >>>
>> >>>     http://xircles.codehaus.org/manage_email
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-mule-user--MQ-Series-and-RFH2-Heading-tf567815.html#a7617225
>> Sent from the Mule - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>

--
View this message in context: http://www.nabble.com/-mule-user--MQ-Series-and-RFH2-Heading-tf567815.html#a9592436
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email