Cameron McCormack:
> Also, I've changed my mind on how I think the DOM 3 interfaces should be
> handled. I think it would be better not to include a copy of all of the
> DOM 3 interfaces in org.apache.batik.dom.dom3 and rather just implement
> and extend whichever level DOM interfaces are available.
One interface that would have to be handled differently, though, is
CustomEvent. Since it extends Event, it won't have the right methods in
it if running under a JDK with DOM 2 interfaces (such as
getNamespaceURI). So the solution would be to have a
sources/org/w3c/dom/events/CustomEvent.java file which was just the same
as the standard DOM 3 CustomEvent.java file except it also has in it the
members of Event that were introduced in DOM 3.
Then, users making custom event objects would be forced to implement all
of the DOM 3 methods, which will be needed by the code in
EventSupport.
Having the CustomEvent.java file in sources/org/w3c/dom/events should
mean it is picked up before the one in the DOM 3 xml-apis.jar (according
to the class path search order specified in the sources/*.mf files).
Cameron
--
e-mail : cam (at) mcc.id.au icq : 26955922
web : http://mcc.id.au/ msn : cam-msn (at) aka.mcc.id.au
office : +61399055779 jabber : heycam (at) jabber.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
