[
https://issues.apache.org/jira/browse/CAMEL-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120118#comment-15120118
]
Karsten Blees commented on CAMEL-9534:
--------------------------------------
I've updated the benchmark to use 100 threads and compare different parser
factory variants (including the methods currently used in Camel, i.e. pooling
factories for StAX and recreating new factories for SAX).
[^0003-CAMEL-9534-XmlConverter-use-a-pool-of-SAXParser-XMLR.patch] should fix
the SAXSource performance issue.
> 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,
> 0003-CAMEL-9534-XmlConverter-use-a-pool-of-SAXParser-XMLR.patch,
> xmlparserbench.7z, xmlparserbench100Threads.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)
