Last month I've committed a changes to the xni.NamespaceContext we've agreed upon.
After the updates, I wonder if NamespaceContext should be a class rather than an interface. Currently this interface has a reset() method that is normally not a part of an interface and it requires that strings are internalized/or added to the SymbolTable. Internally we always use util.NamespaceSupport implementation of this interface and I don't see why would somebody want to implement NamespaceContext in some other way... Given that XNI already has some classes (QName, XMLString) adding one more should not be a problem. Comments? Thank you, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
