I'm probably confused. On the other hand, I doubt I'm the only one who's
confused.
If the Xerces folks say 1.2 is the minimal requirement, I'll take their
word for it. (Most of the folks I know who moved to 1.2 also moved quickly
to 1.3, but most of the useful API changes happened in 1.2 so that's a
reasonable support level.)
As far as Xalan is concerned: We've discussed it often, and I think the
most recent consensus was that it was finally time to stop worrying about
1.1, but I didn't remember a decision to abandon 1.1 actually being made...
and I can't find a statement to that effect on the website. (The XSLTC
support does say that its compiler supports 1.1.8 only at runtime, not
compile time, but...) So as far as I know, Xalan itself is still officially
1.1.8-compatable.... though I don't know whether anyone has tested that in
the past year.
I believe Xalan currently uses JAXP 1.2, so we'll need to make sure it's
compatable with JAXP 1.3...
Again, I'm focusing on Xalan just because that's the other pie I've had my
fingers in; what this really flags is that Apache as a whole should reach
some consensus on what level of JDK APIs is pre-req'd, and every project
should be (a) compatable with that and later JDKs, and (b) clearly
documenting if it's supporting anything earlier.
Nothing wrong with code evolution, as long as the whole eco(de)system stays
balanced...
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
