Our shop develops platform on which multiple core products and customer specific implementations are built. The platform has been around for 5 years and now we are trying to re-think/re-platform. As the platform owner, below are the few key principles I am planning to adhere to
- Be as close as possible to the Java EE spec
- Limit or eliminate dependencies on 3rd party libraries
- Make the contracts explicit of the platform components and if possible make then as osgi compliant bundles
- Be compliant to the standards (for non Java EE stuff)
So we depend lot on JAXP and XSLT for transformations. We had frequent issues with the XSLT style sheets when we were deploying on different vendor app servers and also different versions of the app server from same vendor. Most of开发者_开发知识库 the time the issues are
- Using parser-impl specific stuff in XSLT
- Bundles the parser implementations with-in the app
- Using XSLT 2.0/XPath 2.0 with JAXP 1.3 etc etc
I need some help in below
- Where can I check the compliance of my XSLT's for 1.0 as JAXP 1.4 supports onlty XSLT 1.0 and Xpath 1.0?
- Is there a list of supported finctions etc for XSLT 1.0 (I am looking something similar to javadoc for XSLT and XPath
I need some help in below
- Where can I check the compliance of my XSLT's for 1.0 as JAXP 1.4 supports onlty XSLT 1.0 and Xpath 1.0?
- Is there a list of supported finctions etc for XSLT 1.0 (I am looking something similar to javadoc for XSLT and XPath
One of the best ways to check particular XSLT code for compliance is to use (more than one) compliant XSLT processors. For example, it is almost certain that your code is compliant if it runs successfully with both Saxon 6.5.5 and MSXML4/6.
The standard supported XSLT 1.0 and XPath 1.0 functions are specified in the corresponding specifications. Also this survey by Jesper Tverskov can be very useful.
精彩评论