Hi Elena,

Sorry I have not replied to your message before. I've seen your latest
commit in which you add to the Xerces DOM HTML implementation
non-standard methods that are parts of the HTML interfaces in the Sun
JDK.

One of the concerns I have regarding this change is that if a user
compiles Xerces under Sun JDK and then attempt to use
getContentDocument() method as method on the HTMLFrameElement interface,
Xerces implementation will throw a runtime exception. However, if the
same code is run on IBM JDK, the "NoSuchMethodError" linkage exception will be thrown.


My take on this is that such behavior is not desirable,
since it breaks one of the virtues of Java - "compile once, run
everywhere".


Thanks for your reply. Please help me understand the issue here. 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 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. It is not possible to achieve "compile once , run anywhere" in the context when the APIs are different. So my understanding is that this implementation level change has not changed the scenario. Moreover it would not pose any compilation problem on any JDK.

I believe we need to discuss this change more. Thus, I suggest you pull
back the change (from the main Xerces branch) before the release.



My thinking is that scenario has not changed as a result of this implementation level change. However, If you feel it need some more discussion, I am totally fine with it and would be willing to do necessary changes based on the decision taken. I would appreciate if we see some consenus on it before the next Xerces (2.4) release is out. However, If you feel that there are not any issues now i think we can go out with Xerces ( 2.4 ) release.



thanks, Neeraj


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to