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 >> <[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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
