Hi
I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-6316
On Mon, Apr 22, 2013 at 8:55 AM, Claus Ibsen wrote:
> Hi
>
> Fell free to log a ticket for such an improvement. And as usual
> patches is welcome.
>
>
> On Sat, Apr 20, 2013 at 5:00 PM, j_h_scheufen
> wrote:
>> I just discove
Hi
Fell free to log a ticket for such an improvement. And as usual
patches is welcome.
On Sat, Apr 20, 2013 at 5:00 PM, j_h_scheufen
wrote:
> I just discovered the same thing. Using with a jaxb data format
> produces a byte[] which was not really expected, because the typical use
> case is to
I just discovered the same thing. Using with a jaxb data format
produces a byte[] which was not really expected, because the typical use
case is to have a java.lang.String as input.
I understand that downstream endpoints which expect a java.lang.String can
benefit from Camel's automatic conversi
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
