This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Patch: FYI: disable XML service files


Gary Benson writes:
 > Andrew Haley wrote:
 > > Gary Benson writes:
 > > > Andrew Haley wrote:
 > > > > We don't use Xerces so we can't be compatible with all behaviour
 > > > > in every possible case, but this is far more like to affect
 > > > > user-observable behaviour.
 > > > 
 > > > We should be okay so long as we have either all service files or
 > > > no service files.  The bug we had before was because we had all of
 > > > the service files except one.
 > > 
 > > Out of interest, which one were we missing?
 > 
 > The one I added, org.w3c.dom.DOMImplementationSourceList.
 > 
 > > > However, making xerces work in the classpath like this will mean a
 > > > whole load of things that have both xml-commons-apis and xerces in
 > > > the classpath but not endorsed (eg most everything in Fedora) will
 > > > now be running xerces with libgcj's javax.xml,
 > > 
 > > Which, unless I am very much mistaken, is what has always happened.
 > 
 > No.  Prior to the service files being removed the only way to get
 > xerces to be used was to endorse it.  Until now everything has been
 > using libgcj for both the interface and the implementation.

No, that is certainly not true.  See my prior postings in this thread,
and in particular the test using gcj Version 4.2.  Until this latest
classpath import, we haven't been using the service files in libgcj at
all, so if Xerces was in the classpath we used it.

Andrew.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]