You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by indika kumara <in...@gmail.com> on 2009/11/06 10:22:07 UTC
What should the content-type of the JMS Object Message be ?
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: What should the content-type of the JMS Object Message be ?
Posted by indika kumara <in...@gmail.com>.
Hi Andreas
I haven't familiarized with the code base much so I may completely
wrong. I just want to get advices from one familiar with the code
base.
I thought to create a ObjectDataSource that implements the
javax.activation.DataSource and has an additional method to access the
object directly. Then like BinaryBuilder , wraps within a payload
element -"object".
My requirement is to access object directly inside a mediator and to
put again in a JMS queue (JMS sender) or even to serialize into XML
using XMLEncorder or some utility (to send from another transport).
If you have a better idea , please advice me ...
Thanks
Indika
>
> 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
>> <an...@gmail.com> 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 <in...@gmail.com> 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: dev-unsubscribe@synapse.apache.org
>>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: What should the content-type of the JMS Object Message be ?
Posted by Andreas Veithen <an...@gmail.com>.
On Fri, Nov 6, 2009 at 11:09, indika kumara <in...@gmail.com> 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
> <an...@gmail.com> 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 <in...@gmail.com> 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: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: What should the content-type of the JMS Object Message be ?
Posted by indika kumara <in...@gmail.com>.
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.
Thanks
Indika
On Fri, Nov 6, 2009 at 3:55 PM, Andreas Veithen
<an...@gmail.com> 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 <in...@gmail.com> 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: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: What should the content-type of the JMS Object Message be ?
Posted by Andreas Veithen <an...@gmail.com>.
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 <in...@gmail.com> 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: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org