On Fri, Nov 6, 2009 at 11:09, indika kumara <[email protected]> wrote:
> Thanks Andreas for information... I expects to add the support for
> ObjectMessages in the JMS transport.  What should the best way to add
> this support? Could you please advice me on this.
>
> I thought to create a new Datasource - ObjectDataSource (with one
> additional method to access object directly ) and Builder ... and then
> to use the strategy used in handling BytesMessages.

Can you explain this a bit further? It is not immediately clear to me
how a strategy implemented to handle byte streams can be extended to
Java objects.

> Thanks
> Indika
>
>
> On Fri, Nov 6, 2009 at 3:55 PM, Andreas Veithen
> <[email protected]> wrote:
>> By definition, a content-type is used to describe a payload in
>> protocols that transport an otherwise unstructured byte sequence (or
>> character sequence). Since JMS ObjectMessages and MapMessages (in
>> contrast to BytesMessages and TextMessages) don't fall into that
>> category, they don't have a content-type.
>>
>> Andreas
>>
>> On Fri, Nov 6, 2009 at 10:22, indika kumara <[email protected]> wrote:
>>> Hi all
>>>
>>> What should the content-type of the JMS Object Message be ?. I saw in
>>> a forum that some are using "multipart/*".
>>>
>>> Could someone please advice me on this matter?.
>>>
>>> Thanks Lots
>>>
>>> Indika
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to