gt;>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/JAXB-marshal-generates-byte-array-instead-of-String-tp5715174p5731170.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
>
t; . You'd wish the jaxb data format had a property to
> control the output ...
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/JAXB-marshal-generates-byte-array-instead-of-String-tp5715174p5731170.html
> Sent from the Camel - Us
matic conversion, but if the invoker of the route
expected to get the XML back as a String, you always have to remember to add
. You'd wish the jaxb data format had a property to
control the output ...
--
View this message in context:
http://camel.465427.n5.nabble.com/JAXB-marshal-generates-
Please disregard the comment about conversion issue, a simple refresh on
camel-jaxb in servicemix solved the problem.
BUT, the result of marshal is still a byte[] array while I believe it
should be java.lang.String.
att.
*Henrique Viecili*
On Wed, Jun 27, 2012 at 1:37 PM, Henrique Viecili wrote
Dear Camel Breeders,
would you know any reason why after marshaling an object with jaxb data
format the result BodyType is a byte[] array instead of java.lang.String?
With byte[] I see conversion problems as the log below shows:
12:45:42,474 | WARN | onsumer-thread-5 | JbiBinding
| ?
