We currently have a huge XSLT transformation that takes 20-30 minutes to process. We need to improve the performance and we are considering CDuce. CDuce looks promising. What is a good approach to doing this? Do we have to rewrite the entire xsl logic in CDuce?
相关问题
- Illegal to have multiple roots (start tag in epilo
- Newtonsoft DeserializeXNode expands internal array
- how to use special characters like '<'
- XML - XSLT - document() function inside count() fu
- convert logback.xml to log4j.properties
相关文章
- Creating XML Elements without namespace declaratio
- Get Attribute Value From Simple XML Using JQuery /
- Directly signing an Office Word document using XML
- When sending XML to JMS should I use TextMessage o
- Fragment Content Overlaps Toolbar and Bottom Navig
- Getting “Error: Missing Constraints in ConstraintL
- xslt localization
- Upgrading transaction.commit_manually() to Django
You could rewrite it in another language but there may be easier options, it depends how efficient that XSLT 1 code is. If it uses
//
a lot then it is not uncommon to get orders of magnitude speed improvement by rewriting it not to use//
and to use keys or other constructs instead. Also of course switching to a newer more highly optimised XSLT engine wouldn't hurt. (Your question is tagged xslt 1 but an XSLT2 engine would be able to run it with no or little change)