Ah yes, I understand that. Maybe it would be nice to add the methods defined by Locator2 and Attributes2 without implementing their interface? Then it would be fairly easy to just add the 'implements xx2' statement when you are allowed to. In either case, would you welcome a patch that allows subclassers of AbstractSAXParser to create their own implementation of AttributesProxy and LocatorProxy ? This is the approach I've taken, in order to make my Attributes and Locator support Attributes2 and Locator2, by subclassing the AttributesProxy and LocatorProxy and having AbstractSAXParser call createAttributesProxy() and createLocatorProxy() (protected) functions. In the case that you do not welcome implementing the extension methods, this allows me to provide a subclass of xxxProxy that does, and if you implement them, then my subclasses just list the extension interface in its 'implements' list. If you would welcome either approach I can submit patches for that. -- # Stef Epardaud, # Teachers have potentially more power than military, # Java Defeater # the former can teach us how to not need the latter. # Earth # Lunatech Research, # Solar System # soon we'll quit researching and start finding...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
