> > >>> Thanks, Jan
> > >>>
> > >>>
> > >>>> -Original Message-
> > >>>> From: Fraser Adams [mailto:fraser.ad...@blueyonder.co.uk]
> > >>>> Sent: Tuesday, December 20, 2011 12:46 PM
> > &g
-
> From: "Carl Trieloff"
> To: users@qpid.apache.org
> Sent: Tuesday, December 20, 2011 1:02:32 PM
> Subject: Re: .NET to Java JMS interoperability
>
>
>
> Here is the JMS example
>
> http://qpid.apache.org/books/0.12/Programming-In-Apache-Qpid/html/ch03s0
gt;>> was thinking that for instance specific content-type may trigger JMS
>>> to interpret data as TextMessage. Certainly looking into sources will
>>> help a lot.
>>>
>>> Thanks, Jan
>>>
>>>
>>>> -Original Message-
ta as TextMessage. Certainly looking into sources will
>> help a lot.
>>
>> Thanks, Jan
>>
>>
>>> -Original Message-
>>> From: Fraser Adams [mailto:fraser.ad...@blueyonder.co.uk]
>>> Sent: Tuesday, December 20, 2011 12:46 PM
>&g
:fraser.ad...@blueyonder.co.uk]
Sent: Tuesday, December 20, 2011 12:46 PM
To: users@qpid.apache.org
Subject: Re: .NET to Java JMS interoperability
Hmmm,
That's an interesting in a more general sense with respect to
interoperability.
My suspicion is that there are only a few types that will safel
Or, use the mapped message support in Java(JMS) and.NET. The docs on
that are quite good and it uses the AMQP type system which means you get
full interop across languages, platforms etc.
I know quite a few people use it expressly for JMS <-> .NET message interop.
Carl.
On 12/20/2011 05:04 AM
TextMessage.
Certainly looking into sources will help a lot.
Thanks, Jan
> -Original Message-
> From: Fraser Adams [mailto:fraser.ad...@blueyonder.co.uk]
> Sent: Tuesday, December 20, 2011 12:46 PM
> To: users@qpid.apache.org
> Subject: Re: .NET to Java JMS interoperab
Hmmm,
That's an interesting in a more general sense with respect to
interoperability.
My suspicion is that there are only a few types that will safely
interoperate. Octet arrays are clearly one and I believe that Map
messages are another way to (fairly) safely interoperate. I say fairly
beca
