Bruce D'Arcus wrote:
On Jan 6, 2006, at 5:39 PM, Michael Wechner wrote:
what about making it configurable?
Not if the user has to configure it.
I didn't mean configurable by the user ;-)
I think we need to get to the place where installing XSLT-based
extensions (import/export solutions for example) needs to be as easy
as the extension system is in Firefox. That presupposes that users
don't have to think about "XSLT", much less the processor they are using.
I think the "packaging" goes into this direction, but yes it could be
improved a lot
XSLT 2.0 is a huge advance over XSLT 1.0, and I really don't think
there is any area (performance, conformance, stablity, etc.) in which
Xalan-J is superior to Saxon even in 1.0.
there will always be something "better" and it will never be back and
white only
Perhaps there would be a way to have a simple config file for these
sorts of plug-ins where, if there was a genuine need to use an
alternate processor, a developer could specify that.
that's what I meant or also the usecase of an "integrator" which after
re-configuration deploys it.
Michi
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
