I think we should do a check just before an XPath is evaluated for the first time. Unless all namespace prefixes in the expression are bound, we should throw a NoSuchPrefixException.
We shouldn't care for namespace prefixes of the document, though. Neither should we pull prefix mappings from the document: easy-to-use as it may seem, it can be very confusing. Jan > [....] > I would've thought your XML parser would've complained about a namespace > prefix without a valid URI bound to it. I think Jaxen should probably > be smarter with undefined prefixes, though, to catch cases like this. > Instead of returning null, possibly we should throw a NoSuchPrefixException > or similar from the NamespaceContext translation method. > > I open the floor for discussion... > > -bob _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
