2008/12/22 peter verhaar <peter(_dot_)verhaar1(_at_)gmail(_dot_)com>:
You are far, far better off changing Xalan to Saxon...
Yes, but that's not always an option (e.g. vendor support only xalan
at the moment)
It's usually a far easier option than you think... The reasons for
not using Saxon I usually come across are:
- Never heard of it (despite heavy use of XSLT in the application)
- Confusion with SAX processing
- It's something new / yet another jar / general reluctance for change
Depending on your setup, you should be able to:
- swap in Saxon for Xalan without a problem
- use both, but specifically use Saxon for the transforms under your control
- or at worst some code changes when you use Xalan specifc features
It's all really simple and often takes longer to convince people it's
worthwhile than it does to actually do it.
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--