RE: xml-apis was RE: cvs commit: jakarta-ant build.xml

[Stephane Bailliez <sb...@imediation.com>]

> -----Original Message-----
> From: Edwin Goei [mailto:edwingo@sun.com]

[ dom1.jar, dom2.jar sax1.jar sax2.jar]
> I don't have that much experience w/ working on web 
> applications, but my
> guess would be that splitting API jar files would make the 
> problem more
> difficult as there would be many more combinations.  With a single
> project.jar file containing both API and implementation classes you
> would be sure that the classes within it would all be consistent.

Don't agree. It does not mean we put every jar in it. It means we are able
to pick the right one instead of hacking the jars to remove old interfaces
that could be picked up first. ie, if you are using some code that use sax1,
sax2, dom1 and dom2, then putting sax2.jar and dom2.jar solves everything,
otherwise of course if sax1 or dom1 is picked first you end up with no such
method error or similar.

> Yeah, I don't have much experience w/ third-party tools 
> related to XML,
> but I don't see how this should make a difference.

Flexibility as described above :-)

IMHO Sun should definitely allocate time to jump into library versioning so
that we avoid these collisions in the near future. It will get worse with
time since now we start to have some history in Java development and there
is a good deal of library and version in the field.

Stephane

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>