You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by James Carman <ja...@carmanconsulting.com> on 2012/09/23 01:03:20 UTC
camel-jaxb failing for me locally...
Running org.apache.camel.jaxb.JaxbMarshalNamespacePrefixMapperTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.627
sec <<< FAILURE!
Running org.apache.camel.jaxb.SplitterAndExceptionRouteTwistIssueTest
[Fatal Error] :4:22: An invalid XML character (Unicode: 0x10) was
found in the element content of the document.
[Fatal Error] :1:76: An invalid XML character (Unicode: 0x10) was
found in the element content of the document.
[Fatal Error] :1:76: An invalid XML character (Unicode: 0x10) was
found in the element content of the document.
Re: camel-jaxb failing for me locally...
Posted by James Carman <jc...@carmanconsulting.com>.
Thanks! That is a cool feature.
Sent from my iPad
On Sep 23, 2012, at 5:20 AM, Babak Vahdat <ba...@swissonline.ch> wrote:
> Hi
>
> I just fixed it, so do an update on camel-jaxb which should now make the
> test pass again.
>
> BTW this unit-test verifies a new cool feature in Camel 2.11 provided by
> Claus Ibsen. Thanks!
>
> http://camel.465427.n5.nabble.com/CONF-Apache-Camel-gt-JAXB-td5719722.html
>
> Babak
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-jaxb-failing-for-me-locally-tp5719794p5719799.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: camel-jaxb failing for me locally...
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
I just fixed it, so do an update on camel-jaxb which should now make the
test pass again.
BTW this unit-test verifies a new cool feature in Camel 2.11 provided by
Claus Ibsen. Thanks!
http://camel.465427.n5.nabble.com/CONF-Apache-Camel-gt-JAXB-td5719722.html
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/camel-jaxb-failing-for-me-locally-tp5719794p5719799.html
Sent from the Camel Development mailing list archive at Nabble.com.