Hi Ruwan, Saliya, I want to access the direct JMS Stream, without converting it to OM. The reason here is that JMS->OM conversion would be expensive if we really did not want it. Is there any way I can access the direct byte stream instead of using the converted OM representation?
Thanks, Senaka On Mon, Aug 25, 2008 at 11:40 AM, Saliya Ekanayake <[EMAIL PROTECTED]> wrote: > Ruwan Linton wrote: > > Saliya, > > > > Even the JMS headers are available as message context properties inside > > synapse. > > > Thanks for the info, hmm, then Senaka, I think you problem is pretty > much solved isn't it? I mean you have everything inside the JMS message. > > Thanks > Saliya > > Thanks, > > Ruwan > > > > Saliya Ekanayake wrote: > > > >> As per my knowledge we take the payload and make it available as an > >> OMNode (pls. correct me if I am wrong here). The message builders and > >> formatters, as mentioned by Ruwan, are responsible for this work. So the > >> content inside the JMS message should be available for you. Is this task > >> something that requires accessing data outside the JMS payload? I mean > >> information like JMS headers. > >> > >> Thanks > >> Saliya > >> > >> Ruwan Linton wrote: > >> > >> > >>> Senaka, > >>> > >>> What do you mean by accessing the JMS message directly? Do you want the > >>> byte stream or any of other format of the message? If you need to get > >>> the JMS message as a byte stream then you need to mess around with the > >>> Message Builders and formatters. > >>> > >>> BTW: Cab you please elaborate on your exact requirement? > >>> > >>> Thanks, > >>> Ruwan > >>> > >>> Senaka Fernando wrote: > >>> > >>> > >>> > >>>> Hi all, > >>>> > >>>> After trying out some samples and a bit of debugging, I discovered > >>>> that JMS messages are converted to XML within the message context and > >>>> made available at the mediate() method. Can't I access the JMS message > >>>> directly? > >>>> > >>>> Thanks, > >>>> Senaka > >>>> > ------------------------------------------------------------------------ > >>>> > >>>> _______________________________________________ > >>>> Esb-java-dev mailing list > >>>> [email protected] > >>>> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > >>>> > >>>> > >>>> > >>>> > >>> _______________________________________________ > >>> Esb-java-dev mailing list > >>> [email protected] > >>> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > >>> > >>> > >>> > >>> > >> _______________________________________________ > >> Esb-java-dev mailing list > >> [email protected] > >> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > >> > >> > >> > > > > > > _______________________________________________ > > Esb-java-dev mailing list > > [email protected] > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > > > _______________________________________________ > Esb-java-dev mailing list > [email protected] > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev >
_______________________________________________ Esb-java-dev mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
