Hi Preben,
I was facing the same problem. Seems to be a problem with Weblogic's
TransformerFactory Implementation.
I solved it by specifying an alternate Implementation:
You can either use the system parameter
-Djavax.xml.transform.TransformerFactory= or create a file
META-INF/services/javax.xml.
Super - thanks for the tip.
Best,
Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-XmlConverter-after-upgrade-to-2-12-3-tp5748082p5748381.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yeah - I'll dig into it next week and find a workaround.
I'll post the result back here for others to use.
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-XmlConverter-after-upgrade-to-2-12-3-tp5748082p5748112.html
Sent from the Camel - Users mailing list archiv
Hi
Maybe get in touch with your app server vendor about this?
Not sure why it talks about Java 1.5?
Its an official constant from the JDK
http://docs.oracle.com/javase/6/docs/api/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING
On Fri, Feb 28, 2014 at 12:42 PM, Preben.Asmussen wrote:
> I
I just upgraded a integration running on Weblogic under jrockit 1.6 and found
a problem related to the change in XmlConverter.createTransformerFactory
introduced in 2.12.3.
where the
factory.setFeature(javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING, true);
seems to have sideeffects when runnin
