Hi Everyone,
Thanks for getting back to me with a lot of information about Xalans future.
From what I can gather from the various posts, here is my summary:
XSLT 2.0 was started, but never finished (it would be great to know why...was
it too difficult with the Xalan architecture?).
XalanJ no longer has much of an active contribution base, most of the
developers have gone off to do their own thing on other XML/XSLT projects
(again, would be great to know why, is Xalan considered finished? or too
defective to continue with?)
XalanJ is currently slower than Saxon in most situations, however, this is
possibly just because there's no active work on optimization going on.
So I guess what I'm trying to figure out now is if Xalan is coming to EOL? I
would really like to revive it, and I have some spare development band width to
put towards it, however if heavy weights (IBM) are going to open source a
competing library with a view to killing off Xalan I don't want to lose a bunch
of weekends fighting a losing battle :) (I still don't understand why we end up
with 2 or 3 versions of open source libraries that do exactly the same thing,
it seems a waste of community effort to me, surely we're mature enough to get
our sh&t together :) ).
Having spent quite a bit of time code diving through Xalan, I also think it's a
pretty good product and pretty good code base...and i missing something?? Why
did IBM start again from scratch??
Any thoughts would be appreciated? Is Xalan worth resurrecting and continueing
on with?
__________________________________________________________________________________
Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7.
Enter now: http://au.docs.yahoo.com/homepageset/
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
