This should be fixed now.
On 8/17/06, smokeyjoe <[EMAIL PROTECTED]> wrote:
More information: the "out" NormalizedMessage contained an invalid XML
character. Prroblem was solved by wrapping data in base64 CDATA tag. I now
get a valid log message after successful call to sendSync(). However, I
believe I should still get a valid log message for the remainder of the
MessageExchange.
smokeyjoe wrote:
>
> When I log a MessageExchange before a call to sendSync() I get output:
>
> MessageExchange[
> id: ID:B-0320-2587-1155829316188-28:0
> status: Active
> role: consumer
> service: {http://nettoolkit.gestalt.com/encoding}encoding
> in: <?xml version="1.0" encoding="UTF-8"?><UOB version="0.5">.......
>
> After a succesful call to sendSync() I get output:
>
> null
>
> Here is my code:
>
> log.debug("sending MessageExchange\n" + encodingInOutME);
> this.context.getDeliveryChannel().sendSync(encodingInOutME);
> log.debug("received MessageExchange\n" + encodingInOutME);
>
> The MessageExchange is valid and can be successfully processed. Any ideas?
>
>
--
View this message in context:
http://www.nabble.com/MessageExchange.toString-returns-%22null%22-after-call-to-sendSync%28%29-tf2122977.html#a5858236
Sent from the ServiceMix - User forum at Nabble.com.
--
Cheers,
Guillaume Nodet
