Because both are parsing and this part of process is statefull, so somehow
they are more like builders not factories ;).
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JAXB-DataFormat-is-not-thread-safe-tp5737748p5737883.html
Sent from the Camel - Users mailing list ar
It looks like the Xerces SchemaFactory is also NOT thread-safe [1].
[1]
http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/validation/SchemaFactory.html
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Cam
I will add some notes to the Camel JAXB WIKI page later today about the fix
and a potential workaround for previous versions.
Best,
Christian
Am 23.08.2013 08:41 schrieb "Hack Kampbjørn" <
camel.us...@list.hack.kampbjorn.com>:
> A workaround is to use a SchemaFactory implementation that is thread
A workaround is to use a SchemaFactory implementation that is thread safe. The
one bundled in JDK is not but the one in Xerces is.
On 2013-08-22, at 12:38, solimo wrote:
> Oh, how could I miss CAMEL-6630. Thanks.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com
Oh, how could I miss CAMEL-6630. Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JAXB-DataFormat-is-not-thread-safe-tp5737748p5737759.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
This is fixed by CAMEL-6630
On Thu, Aug 22, 2013 at 10:56 AM, solimo wrote:
> Hello!
>
> Recently, I've encountered an issue (I suppose) connected with Camel's
> DataFormat implementation - the JAXB one. Due to exhausting tests, which we
> currently perform we've noticed that Camel's implemen
