I have to agree with Elena here. Poluting our code to allow one to ignore our compilation framework and compile against a broken JDK doesn't sound reasonable to me. -- Arnaud Le Hors - IBM, XML Standards Strategy Group / W3C AC Rep.
> -----Original Message----- > From: Elena Litani [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 25, 2003 8:00 AM > To: [EMAIL PROTECTED] > Subject: Re: Xerces DOM HTML impl [was: Re: [GUMP] Build Failure - > xml-xerces] > > > Hi Neeraj, > > Thank you for the reply. > > Neeraj Bajaj wrote: > > My > > understanding is that since it is an implementation level change it > > doesn't make difference. Had these changes not been done , any > > application which has used getContentDocument() is compiled against SUN > > JDK and run against IBM JDK would still be getting "NoSuchMethodError". > > I am not sure I understand. Before your changes, applications could not > have used getContentDocument() since this method did not exist in Xerces > implementation nor in the xml-apis.jar. But even if an application would > attempt to use getContentDocument() before your change, it would have > failed to compile under both JDKs: under Sun since Xerces does not > provide implementation of this method, and under IBM one since this > method is not defined on the interface. Given that any application code > written AND compiled under either JDK would run the same. > > By adding this method, first, we *pretend* as we implement this method > which we don't and I think this might give people false hopes that we > might implement this method in the future. > Second, an application that uses HTMLFrameElement.getContentDocument() > now can compile under Sun JDK, but compiling such code using Ant or IBM > JDK will fail. > > Talking about compiling directly, I would be very surprised to find > people who actually don't use Ant. To build Xerces we do all kind of > tricks in the build.xml file (excluding some files, for example) so how > would someone achieve the same by compiling directly..? Thus, in my > opinion, people compile Xerces only using Ant and thus there is no > reason to add these method and potentially make applications depend on > the level of JDK it was compiled and run against. > > I hope I've convinced you that we don't need this change :). If not, I > don't think we have time to reach consensus before the release. So I > would suggest again to remove this change and continue the discussion > after the release (potentially changing the code in the next Xerces > release). > > Anyone else has an opinion on this issue? > > > > I think the concern you are raising is there because of a different > > reason. It seems there is difference in DOM HTML apis part of two JDKs. > > Just to point out that the xml-apis.jar contains are the official DOM > Level 1 HTML interfaces plus an extra DOM L2 interface > DOMHTMLImplementation. On the other hand, the DOM HTML interfaces > shipped in Sun JDK are hybrid between DOM L1 and DOM L2 HTML and could > not be mapped to any official DOM version. > > > Thank you, > -- > Elena Litani / IBM Toronto > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
