Hi Neeraj, Neeraj Bajaj wrote: > So, idea of removing > redundant method calls is good, though i wont like to see this method be removed > from XMLDocumentHandler interface. XNI is separate set of APIs like SAX,DOM to > pass XML information to the application. So for those APIs to be complete, IMO, > it should be part of XMLDocumentHandler interface as it is.
Why do you think that API won't be complete? IMO, the API is complete -- the information is not lost but retrieved via XNI property mechanism instead of XNI events. I understand that keeping start/end prefix makes the XMLDocumentHandler look a lot like SAX... but I don't think this is necessary. > However, lets see other side of it, in worst case scenario, there can be > three component in pipeline for which there would be 6 (redundant) calls for > each namespace declarations. So, we should take care of this issue in *our* XNI > implementation. One way can be , we can leave the implementaion of this method > empty in our various compoents and our parser generaters > AbstractSAXParser/AbstractDOMParser can do the job of passing this information > to the application via NamespaceContext object as you suggested. For XNI > parsers, probably it can be taken care in AbstractXMLDocumentParser.. Need to > think more on it. That is exactly what I want to avoid. You are suggesting to specify that namespace binding XNI calls won't be issued by some *core* components but might be issued by others. IMO, we will get on a slippery slope if we start defining which components are core and which are not. Given that each component is just an implementation of an interface, we can't specify which subset of the components is not going to issue the events. And even if we do specify it, user who programs to the XNI will still need to use the property if s/he needs reliable access to the namespace binding (because it is possible that s/he extends some configuration that includes component that won't issue the start/end prefix events). So .. in the end everybody who wants namespace information will need to use this property anyway, so the XNI events are redundant. Thank you, -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
