---- "Gary L Peskin" <[EMAIL PROTECTED]> ---- > Have a look at http://java.sun.com/xml/jaxp/faq.html#pluggability.
I don't know whether to laugh or cry. Here's the first time that I've ever seen an official bit of Sun documentation address this issue at all - Good. But reading it, note the Bad phrase they use: "For example, updating Java 2 SDK 1.4 with a newer version of Xalan may not be as simple, unless the TransformFactory subclass uses a different name from the bundled version within Java 2 SDK 1.4. There is an Endorsed Standards mechanism that may work in this case." Which basically means we 'may' be able to rev newer Xalan versions, but I wouldn't count on it being easy. It all comes down to actually trying it and reporting results, which unfortunately I don't have time for quite yet. I'm not going to believe you can just dump a new xalan.jar in the lib/endorsed directory and have it work until I see it with my own eyes. One other complication will be the fact that in many situations it'll come down to classloaders, not properties or services files, that determine which Xalan version is loaded. JAXP lets you override the implementation classname all you want - but if the Xalan classname in rt.jar is the same as the one in our-next-xalan-version.jar, then guess which one will probably be loaded first? It would also be nice if Sun coordinated or at least informed the Xalan community on when they're planning to take a code snapshot, but I haven't seen that happening lately in any official or semi-official way. ===== - Shane <eof aka="mailto:[EMAIL PROTECTED]"; .sig="Du sublime au ridicule il n'y a qu'un pas." /> __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com
