Joe,
the idea of dropping support for JRE 1.1.8 ( indeed 1.1.x) was proposed on
the mailing lists with no negative responses. The response was essentially:
"about time this was done". The Xalan PMC voted on the issue and the motion
was passed. So now only 1.2 and up is supported as a runtime environment.
Since then a number of patches from Dave Brosius doing exactly what you
suggest were applied. Also in the last days other synchronization issues in
XALANJ-2344 and XALANJ-2336 also due to an over use of java.util.Vector
were applied to the code base.
The rest of the java.util.Vector, or other old over-synchronization will
probably be left alone unless it is a performance issue.
- Brian
[EMAIL PROTECTED]
m
To
11/17/2006 04:44 xalan-dev@xml.apache.org
PM cc
xalan-dev@xml.apache.org,
xalan-j-users@xml.apache.org
Subject
Re: Performance problem for Xalan-J
on intel-dual core
We've known for a while that some part of Xalan are oversynchronized, due
to their use of the original Java heap and vector classes -- but we
couldn't move to the unsynchronized 1.2 Collection classes because we were
still committed to running on Java 1.1.8.
Now that Xerces has given up compatability with that version -- and I think
Xalan is doing likewise? -- it might be interesting to see what effect a
global replace of the old classes with their new versions would have on the
system. I don't think we're actually relying on their built-in
synchronization anywhere; the few places I can think of where we do some
inter-thread coordination are explicitly synchronized at the functional
level.
This cut-over would involve a lot of fiddling detail work, but should be
straightforward...
______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (
http://www.ovff.org/pegasus/songs/threes-rev-11.html)
