Hmmm. That link doesn't seem to be helping me much. Can you point me to some code to look at?
On 4/6/09 4:32 PM, "Andreas Veithen" <[email protected]> wrote: > My guess is that there is in issue in the detection of the content > type of the message and that the JMS transport thinks the message is > text/plain. Note that the way the content type is determined has > changed since 1.2 (which used some rather weird way of doing this). > Please have a look at the documentation of the > transport.jms.ContentType parameter in [1]. > > Andreas > > [1] http://people.apache.org/~veithen/transport/jms.html > > On Mon, Apr 6, 2009 at 22:14, Keith Bohnenberger > <[email protected]> wrote: >> Sorry for not including that .... >> I'm using a SNAPSHOT from last week. >> >> >> On 4/6/09 4:12 PM, "Andreas Veithen" <[email protected]> wrote: >> >>> Which version of Synapse are you using? >>> >>> Andreas >>> >>> On Mon, Apr 6, 2009 at 22:05, kbohnenberger >>> <[email protected]> wrote: >>>> >>>> I have a proxy mediator with a JMS transport set. >>>> I have logging turned on to show the messages that gets received. >>>> When the messages gets printed, all the "less than" symbols after the "<xml >>>> ..." tag show up as </ but the "greater than" symbols show up as ">" >>>> >>>> I'm pretty sure the messages are correct on the queue because I can listen >>>> with a "stand alone" generic JMS listener outside of the ESB and print the >>>> messages. When the generic JMS listener prints the messages, they look >>>> fine. >>>> >>>> Ultimately I'm trying to run an xpath over the incoming messages but the >>>> xpath always returns 0 elements. I'm thinking it's because of the "<" >>>> instead of the "<" >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/jms-transport-tp22916189p22916189.html >>>> Sent from the Synapse - User mailing list archive at Nabble.com. >>>> >>>> >> >> This communication, along with any attachments, is covered by federal and >> state law governing electronic communications and may contain company >> proprietary and legally privileged information. >> If the reader of this message is not the intended recipient, you are hereby >> notified that any dissemination, distribution, use or copying of this message >> is strictly prohibited. >> If you have received this in error, please reply immediately to the sender >> and delete this message. Thank you. >> >> This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you.
