jaxp investigation

[Tom Tromey <tromey at redhat dot com>]

I've been looking into JAXP this week, trying to see what to do.  I
can't say I fully understand the situation.

The current JDK releases incorporate JAXP into their distributions,
and real programs (eclipse) rely on this.  So, as a baseline we want
to include it as well.

Now, historically we made separate lib-org-xml-sax and lib-org-w3c-dom
libraries to work around duplicate class registration bugs if the user
tried to use xerces.  Nowadays, though, testing on the JDK shows that
classes from these libraries is loaded by the bootstrap class loader
-- meaning that the only way for the user to override these choices is
to have a special non-delegating class loader.

So, I think it would make sense for us to incorporate JAXP, SAX, and
w3c.dom directly into libgcj.so.

I plan to do this in the very near future.  If you know of some reason
why we shouldn't do this, please speak up asap.

Tom