Then there should be 2 separate implementations. They can delegate to common helper classes when possible, but emphasis should be on ease of use, not ease of implementation.
The current solution makes it impossible to mix components that depend on different versions of the same package. So if I wrote a component that uses org.w3c.dom from one day before the DOM 2 support was added, it can't work with a component written the next day. ----- Original Message ----- From: "Arnaud Le Hors" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Monday, April 24, 2000 4:22 PM Subject: Re: Build questions > Eric Hodges wrote: > > > > I see. Then I think they should have made an entirely new package for DOM 2 > > that shares no dependencies with DOM 1. > > Although this would work for applications it would be impossible for an > implementation to implement both packages with the same classes; because > you end up with similar methods with a different return type. Major > bummer! > -- > Arnaud Le Hors - IBM Cupertino, XML Technology Group
