qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Stevenson <matt.r.steven...@gmail.com>
Subject Re: Setting BytesMessage content type
Date Thu, 21 Jul 2011 20:33:21 GMT
The "x-jms-type" header looks like some sort of placeholder.  I couldn't
find it in the specs or used by other projects.
This can easily be fixed by having get/setJMSType(..) call
get/setContentType(..) in AMQMessageDelegate_0_10.java.

Should I submit a patch?

On Thu, Jul 21, 2011 at 12:32 PM, Gordon Sim <gsim@redhat.com> wrote:

> On 07/21/2011 08:48 AM, Matt Stevenson wrote:
>
>> Hi,
>>
>> I'm sending a BytesMessage from Java to C++ and I ran into a little
>> trouble
>> with content type.
>> In my Java client code I am using a javax.jms.BytesMessage from the
>> geronimo-jms_1.1 library.
>> The BytesMessage only has methods for get/setJMSType( ), and not
>> get/setContentType( ).
>> If I set the JMSType in Java, it does not change the contentType in C++.
>>
>> I can work around this by casting the BytesMessage to a qpid
>> JMSBytesMessage.  Then I can use setContentType( ), which shows up on on
>> the
>> C++ side.
>>
>>  From the documentation I was expecting setJMSType to set the contentType.
>>>
>> Looking at the code, it sets the "x-jms-type" message header.
>>
>> Should setJMSType actually set the contentType?
>>
>
> That does sound reasonable to me.
>
> ------------------------------**------------------------------**---------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.**apache.org<users-subscribe@qpid.apache.org>
>
>


-- 
Matt Stevenson.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message