Hi Claus, As you said, I don't think that issue is related to this one. I think my issue is specific to the way JBI exchanges are handled within Camel...
Claus Ibsen wrote: > > Hi > > This might not at all be related, but beware that Vadim had some really > strange issues with xstream. He had to set some kind of file encoding with > -D to the JVM to get it working. > > http://issues.apache.org/activemq/browse/CAMEL-924 > > But I don't think he used JBI though. > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > > -----Original Message----- > From: Gert Vanthienen [mailto:[EMAIL PROTECTED] > Sent: 23. oktober 2008 13:37 > To: [email protected] > Subject: Re: XStream with JBI > > L.S., > > What is the exception or error you are getting? We should definitely > support this use case out-of-the-box... > > Regards, > > Gert > > raulvk.soa wrote: >> Hi, >> >> I am using Camel embedded in ServiceMix. My camel route receives a JBI >> message, turns it into a Java Object by using XStream and then passes it >> on >> to iBATIS. >> >> However, I am facing problems with the XStream processing. I suspect that >> these are derived from the fact that the underlying Camel Exchange is >> actually a JbiExchange which only accepts XML as the in and out body >> messages. >> >> Therefore, I need to get rid of all the Jbi stuff and simply use a >> standard >> Camel Exchange which will allow me to set an Object as the in message. >> >> Is it possible to do so out of the box? >> >> Thanks! >> > > > -- View this message in context: http://www.nabble.com/XStream-with-JBI-tp20129124s22882p20129407.html Sent from the Camel - Users mailing list archive at Nabble.com.
