This stuff just drives me crazy. I'm hunting it for 3 days. Current release camel is quite unusable with the bug when logger shuts down when message body is null. So I have to switch to current camel snapshot (built by myself).
At the moment I know that if I link my test application to the camel-xstream, it works as expected. But when I link directly to camel-xstream.jar then output of marshaler becomes null. Any hints how jar hell problems are troubleshooted? Vadim. On Thu, Sep 18, 2008 at 9:00 AM, Vadim Chekan <[EMAIL PROTECTED]> wrote: > No, it is not released yet. I'm just running ahead :) > > > Claus Ibsen wrote: >> >> Hi >> >> No. But since its an upgrade then it could be some classpath issues with >> duplicate .jars on the classpath. Please make sure your classpath is clean >> and correct. >> >> BTW: I haven't seen any announcement on activemq v5.2 being released. Is >> it an official release you are using? Is it in the central maven repo? >> We should have a ticket to upgrade camel as well then. >> >> >> Med venlig hilsen >> Claus Ibsen >> ...................................... >> Silverbullet >> Skovsgårdsvænget 21 >> 8362 Hørning >> Tlf. +45 2962 7576 >> Web: www.silverbullet.dk >> -----Original Message----- >> From: Vadim Chekan [mailto:[EMAIL PROTECTED] Sent: 18. september 2008 >> 00:46 >> To: [email protected] >> Subject: xstream marshalling >> >> I'm having problem with xstream again. >> I upgraded to activemq-5.2.0 and all the sudden marshaller returns empty >> body. >> And there is no errors at all. >> Does anybody know what could be wrong? >> >> > > -- >From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT is explicitly specified
