Yes, we changed the default setting in Camel-2.12.x to enforce the security
the setting by default.
You can override the setting just as Grzegorz suggested.
--
View this message in context:
http://camel.465427.n5.nabble.com/XMLConstants-FEATURE-SECURE-PROCESSING-feature-setting-in-jboss-fuse-6-
Fuse 6.1 uses Camel 2.12, Fuse 6.0 used Camel 2.10.
Look at https://issues.apache.org/jira/browse/CAMEL-7123 - from Camel 2.11
Camel sets:
factory.setFeature(javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING, true);
if you want to change this behaviour, configure your XSLT endpoint by
referencing
Hi
This is the Apache Camel user forum.
If you want to discuss JBoss Fuse product then use the jboss forum at
https://community.jboss.org/en/jbossfuse
On Wed, Apr 30, 2014 at 9:09 AM, bharadwaj wrote:
> The solution is not proper.. and it's perfectly working in jboss fuse 6.0
> even with same v
The solution is not proper.. and it's perfectly working in jboss fuse 6.0
even with same version.
--
View this message in context:
http://camel.465427.n5.nabble.com/XMLConstants-FEATURE-SECURE-PROCESSING-feature-setting-in-jboss-fuse-6-1-tp5750712p5750715.html
Sent from the Camel - Users mailin
Hello Satyam
The problem is related to
https://jaxp.java.net/1.4/JAXP-Compatibility.html#JAXP_security which
defaults to true in JAXP 1.4.
See also this post:
http://camel.465427.n5.nabble.com/camel-validator-parser-doesn-t-allow-a-maxOccurs-attribute-value-to-be-set-greater-than-the-value-5-0-td
Hi,
I have a project jar which when deployed in jboss-fuse-6.0 works fine for
all request.
But when I deploy the same jar in jboss-fuse-6.1 and try to hit the same
requests, I am getting the following error in logs:
CaughtExceptionType: javax.xml.transform.TransformerException,
CaughtExceptionMe
