OK, I'm not even going to try that. The complexity of building against 2 versions of the same package is nightmarish. I won't inflict that on the rest of my organization, or the people who use my code.
----- Original Message ----- From: Eric Hodges <[EMAIL PROTECTED]> To: <[email protected]>; <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Tuesday, April 25, 2000 1:52 PM Subject: Re: Build questions > Very interesting, I had no idea Java 2 did this. > > The problem is that (I'm pretty sure) Xalan and Xerces call the > unimplemented methods in my Document. I'll make sure in about 30 minutes > when I get to my other system. > > ----- Original Message ----- > From: "Arnaud Le Hors" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[email protected]> > Sent: Tuesday, April 25, 2000 1:11 PM > Subject: Re: Build questions > > > > Eric Hodges wrote: > > > > > > How so? And how do you load the DOM level 2 interface "first"? > > > > In Java 1.1, at the time the jvm loads the classes it will barf if a > > class doesn't fully implement the interfaces it claims to implement. > > This makes it impossible to mix a DOM Level 2 implementation with a DOM > > Level 1 one. On the other hand Java 1.2 doesn't enforce this. It will > > happily load DOM level 1 classes with DOM Level 2 interfaces. As long as > > you do not try and use these classes as DOM level 2 classes you're fine. > > To load the DOM Level 2 interfaces first, all you have to do is to make > > sure they are in your classpath before the level 1 at runtime. > > > > Note that you still need to have the right interfaces at compile time. > > But this can be accommodated. > > -- > > Arnaud Le Hors - IBM Cupertino, XML Technology Group >
