DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11792>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11792 XPathAPI throws NPE If Any Extension Function Used ------- Additional Comments From [EMAIL PROTECTED] 2002-08-19 18:37 ------- I'm not sure the current default behavior is exactly a bug, since avaiability of extensions (and which extensions are supported) is up to the environment; XPath itself leaves that completely up to the implementation and/or the calling environment. But I agree that we should provide a way for the caller to specify an ExtensionProvider (which I'd call a request for enhancement), and we should recover more cleanly when one isn't available (which I agree is a bug). In the case of the specific expression cited: You'd also need to plug in a namespace resolver which knew how to map the "regexp:" prefix in your expression into the proper namespace URI for the ExtensionProvider's look-up. Note that defining the prefix in the source document is *not* sufficient unless you have a resolver which explicitly says how to check with the source doc; prefixes may be mapped differently in different contexts.
