You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Ruwan Linton (JIRA)" <ji...@apache.org> on 2008/06/26 13:47:45 UTC
[jira] Created: (SYNAPSE-378) Improve the performance of the XSLT
mediator
Improve the performance of the XSLT mediator
--------------------------------------------
Key: SYNAPSE-378
URL: https://issues.apache.org/jira/browse/SYNAPSE-378
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: 1.2
Reporter: Ruwan Linton
Assignee: Andreas Veithen
XSLTMediator performance can be further improved by using various methodologies and the idea is to enable a configuration point where a user can specify the optimized methodology for his configuration.
Some of the methodologies will be Stax based Source, StreamSource and StreamResult, and so on... It is better if we can write an AXIOMSource and AXIOMResult pair which should give the best performance :-)
Also we can use features to enable these methodologies, and it is obvious that only one of these set of features can be used for a given XSLT config and we might introduce a priority level so that if two of these features are used highest priority one will be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-378) Improve the performance of the XSLT
mediator
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned SYNAPSE-378:
---------------------------------------
Assignee: Ruwan Linton (was: Andreas Veithen)
Implementation of AXIOMSource/Result is not completed, so we are ready for a new round of performance tests.
> Improve the performance of the XSLT mediator
> --------------------------------------------
>
> Key: SYNAPSE-378
> URL: https://issues.apache.org/jira/browse/SYNAPSE-378
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2
> Reporter: Ruwan Linton
> Assignee: Ruwan Linton
>
> XSLTMediator performance can be further improved by using various methodologies and the idea is to enable a configuration point where a user can specify the optimized methodology for his configuration.
> Some of the methodologies will be Stax based Source, StreamSource and StreamResult, and so on... It is better if we can write an AXIOMSource and AXIOMResult pair which should give the best performance :-)
> Also we can use features to enable these methodologies, and it is obvious that only one of these set of features can be used for a given XSLT config and we might introduce a priority level so that if two of these features are used highest priority one will be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-378) Improve the performance of the XSLT
mediator
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609121#action_12609121 ]
Andreas Veithen commented on SYNAPSE-378:
-----------------------------------------
The strategy to build Source and Result objects can now be selected by adding the following elements to the mediator configuration:
<attribute name="http://ws.apache.org/ns/synapse/transform/attribute/sbf" value="org.apache.synapse.util.jaxp.AXIOMSourceBuilderFactory"/>
<attribute name="http://ws.apache.org/ns/synapse/transform/attribute/rbf" value="org.apache.synapse.util.jaxp.StreamResultBuilderFactory"/>
(Note that this is a temporary solution; we can agree later on what is the best way to configure/select the strategies.)
There are four strategies to build the Source:
org.apache.synapse.util.jaxp.AXIOMSourceBuilderFactory (experimental)
org.apache.synapse.util.jaxp.DOOMSourceBuilderFactory
org.apache.synapse.util.jaxp.SpringStaxSourceBuilderFactory
org.apache.synapse.util.jaxp.StreamSourceBuilderFactory
There are two strategies to build the Result:
org.apache.synapse.util.jaxp.DOOMResultBuilderFactory
org.apache.synapse.util.jaxp.StreamResultBuilderFactory
AXIOMSourceBuilderFactory is incomplete but there should be enough support to run the performance tests. All strategies except DOOMSourceBuilderFactory work with Saxon (I solved the problem with Spring's StaxSource by upgrading to a new version of spring-xml.jar).
Ruwan, can you rerun the performance tests?
> Improve the performance of the XSLT mediator
> --------------------------------------------
>
> Key: SYNAPSE-378
> URL: https://issues.apache.org/jira/browse/SYNAPSE-378
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2
> Reporter: Ruwan Linton
> Assignee: Andreas Veithen
>
> XSLTMediator performance can be further improved by using various methodologies and the idea is to enable a configuration point where a user can specify the optimized methodology for his configuration.
> Some of the methodologies will be Stax based Source, StreamSource and StreamResult, and so on... It is better if we can write an AXIOMSource and AXIOMResult pair which should give the best performance :-)
> Also we can use features to enable these methodologies, and it is obvious that only one of these set of features can be used for a given XSLT config and we might introduce a priority level so that if two of these features are used highest priority one will be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org