[ https://issues.apache.org/jira/browse/JXPATH-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Benson resolved JXPATH-61. ------------------------------- Resolution: Won't Fix Fix Version/s: (was: 1.3) Final result: reverting related changes per majority consensus on this thread with strong influence from ERH as a recognized expert in the XML field. See http://marc.info/?l=jakarta-commons-dev&m=117193684907951&w=2 > [jxpath] Default Namespace not handled correctly > ------------------------------------------------ > > Key: JXPATH-61 > URL: https://issues.apache.org/jira/browse/JXPATH-61 > Project: Commons JXPath > Issue Type: Improvement > Affects Versions: 1.2 Final > Environment: Operating System: All > Platform: All > Reporter: Richard Unger > Priority: Minor > > JXPath 1.2 does not handle the default namespace correctly. There is no way to > set the default namespace on a context, so xpath expressions with unprefixed > node-selections do not match the default namespace. > Eg: > <?xml version="1.0" encoding="iso-8859-1"?> > <test xmlns="http://test"> > <child-element /> > </test> > This is valid xml, with default namespace 'http://test' > If the following xpath expression is used: '/test/childelement', it will not > match the child-element element in this xml file. > There appears to be no way to use the function > JXPathContext.registerNamespace() > to associate a default namespace with the context. > The programmer is forced to introduce a namespace prefix for JXPath, the xpath > expression 'foo:test/foo:child-element' will correctly match the element if > JXPathContext.registerNamespace("foo","http://test") is called first. > This is, IMHO, a bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]