JBoss development,
A new message was posted in the thread "Removing xalan.jar":
http://community.jboss.org/message/524324#524324
Author : Richard Opalka
Profile :
http://community.jboss.org/people/richard.opalka@jboss.com
Message:
--------------------------------------------------------------
I d
on't wanna sound PITA and I know this is the never ending story discussion
but why we're still not removing it?
*I think it's time to remove xalan from JBoss or at least from endorsed directory.*
I came to this when I started analyzing
https://jira.jboss.org/jira/browse/JBWS-2917
So my question is does some project depend on packages:
* org.apache.xalan.*
* org.apache.xml.*
* org.apache.xpath.*
from xalan.jar or it's problem of JVM incorporating buggy implementation of it?
I see from
https://jira.jboss.org/jira/browse/JBAS-2073
that in the past there used to be a buggy implementation in JDK 4.
According to
http://community.jboss.org/message/346954#346954
there used to be some issues in the past when endosing xalan.jar
together with xml-apis.jar on JDK5.
But now xml-apis.jar isn't endorsed any more and we're just supporting JDK6 and
above.
I also see we're using some brew version of it (incorporating some xalan patches).
The issues these patches are trying to solve are also in implementation of supported
JVMs?
I found that JBossWS depends on xalan
https://jira.jboss.org/jira/browse/JBWS-2919
(should be fixed soon).
How about other projects? Do MC, JBossXB or some other projects depend on xalan
directly?
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/524324#524324