[ https://issues.apache.org/jira/browse/CAMEL-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116500#comment-15116500 ]
Daniel Kulp commented on CAMEL-9534: ------------------------------------ -1 on the first part.... The performance issue is not so much the time of the parsing, but the fact that NOT using StAX involves a global synchronized lock on the parser factories which causes major performance problems when using 10's - 100's of threads. If there is an issue with StAXSource, try using the StaxSource (that your patch removes) with possible extra config on it to have it map CDATA to plain characters if necessary. > XsltComponent: fix support for Saxon-B (and Woodstox) > ----------------------------------------------------- > > Key: CAMEL-9534 > URL: https://issues.apache.org/jira/browse/CAMEL-9534 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-xslt > Affects Versions: 2.11.4, 2.12.3, 2.13.0, 2.14.0 > Reporter: Karsten Blees > Attachments: > 0001-CAMEL-9534-XsltComponent-set-default-of-allowStAX-op.patch, > 0002-CAMEL-9534-XsltComponent-fix-support-for-Saxon-B-and.patch, > xmlparserbench.7z > > > AFAIK Saxon-B is the only XSLT 2 processor that supports Java extensions > (that's why it is still available for download on the Saxon site). > CAMEL-7130 enabled the "allowStAX" option by default, which is not supported > by Saxon-B. This also breaks handling of CDATA sections with the Woodstox > StAX implementation. > CAMEL-7753 tries to configure Saxon's MessageWarner class via a proprietary > Saxon API that seems to change frequently - the current code only works with > Saxon 9.3 - 9.5 (see also CAMEL-7891, CAMEL-8830). -- This message was sent by Atlassian JIRA (v6.3.4#6332)