Re: [cross-project-issues-dev] One more late breaking change: planning t

[David M Williams <david_williams@xxxxxxxxxx>]

org.w3c.dom has been removed, beginning
with this week's Stable Orbit build 
http://download.eclipse.org/tools/orbit/downloads/drops/S200705301823/

In many cases, we've just been able
to remove our minor dependancy on it, 
if we assume we are running in Java
1.5 JREs (which we do anyway, for all practical purposes). 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=189716

If someone happens to redistribute it
for Europa RC2 (with the original xerces) I don't think 
there will be any harm, but there will
be a new xerces "in the stack" that has all 
those interfaces moved into it, and
re-exported). 

Test early, test often :)

David M Williams/Raleigh/IBM@IBMUS
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

05/29/2007 06:22 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	cross-project-issues-dev@xxxxxxxxxxx
cc
Subject	[cross-project-issues-dev] One more late breaking change: planning        to remove org.w3c.dom

This bundle, org.w3c.dom consists of interfaces from three standards, org.w3c.dom,
javax.xml, and org.sax.xml, and come from the org.apache.xerces implementation
of 
those interfaces. Collectively, they are all part of JAXP 1.3 and the Xerces
version is compatible with the JRE versions, but does have a few small
differences. 

This was put in Orbit as a separate bundle since Xerces ships the implementation
in one jar, and these interfaces in another jar (xml-apis.jar). But, the
current org.w3c.dom bundle is not quite right. 
Some have requested the three families of interfaces be separated out into
three separate bundles, and if we do that, then anyone who starts to use
the org.w3c.dom bundle would be broken in the future. And, we can't do
that.  The current version is not very useful, either, since it doesn't
export version numbers for its packages. 

While it was hoped to get all this sorted out for this release, I just
haven't had time, and it's not a "stop ship" sort of requirement.

So, I'd like to put that xml-apis.jar back in the xerces bundle (and still
export those interfaces from there, as is currently true). 

What's it matter to you? Not much, unless you currently "require bundle"
org.w3c.dom. If you do, you'll have to change to use "require bundle"
org.apache.xerces, if you really need it. 

There's only two cases in Europa that I can find (outside of WTP) that
use org.w3c.dom and that's in DTP, 

org.eclipse.datatools.enablement.oda.ws 
org.eclipse.datatools.enablement.oda.ws.ui 

Since these two bundles import wsdl4j, I suspect they were following our
WTP model (advise?) which has turned out to not be needed at all. So, 
hopefully you can just remove org.w3c.dom. At worst, you'd have to change
to org.apache.xerces. 
See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=189716

So, unless anyone has a good reason not too, I'll remove this bundle from
Orbit, and simply make it part of the xerces bundle. This basically puts
us right back to the way we've done things in previous releases ... we'll
re-evaluate next release if more is needed. 

Feel free to ask questions or let us know if this impacts you. 

Thanks, _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev