commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitri Plotnikov" <>
Subject Re: [JXPath] Context Namespace-Relative Queries (v1.2)
Date Sun, 17 Apr 2005 15:24:46 GMT

You are not the first to raise this issue.  See for example the discussion 
in this bug report:

I think it's time we finally resolve the problem.

We have come up with three alternative solutions so far:

1. Using "null" for namespace prefix.  I don't necessarily like the idea - 
it feels atrificial and it blocks access to elements that have no namespace 
at all.

2. We introduce this new method on JXPathContext:


Then whenever a name is used without prefix in an XPath, this default 
namespace is assumed.  This is effectively the same as 1, except that 
aestetically this looks better.  Unfortunately this solution has the same 
problem: you can no longer reference elements that really don't have any 

3. We introduce this other method on JXPathContext:
   context.setNamespaceIgnored(ns, boolean)

This would allow us to register one or multiple namespaces that should be 
ignored altogether.  Let's say
 - you call context.setNamespaceIgnored("abc", true)
 - you have a document that looks like this:

 <foo xmlns:names="abc">

- and you try to resolve the xpath "//a"

This path will return both elements: x and y, one because it does not have a 
namespace and the other because its namespace is ignored.

This third option is my favorite.

What do you think?


- Dmitri

----- Original Message ----- 
From: "Michael Nestler" <>
To: <>
Sent: Thursday, April 07, 2005 1:08 PM
Subject: [JXPath] Context Namespace-Relative Queries (v1.2)

> Hello,
> I recently had to switch from JXPath 1.1 to 1.2 in order to benefit
> from some bug fixes. I am using JDOM 1.0. It appears that JXPath's
> behavior regarding namespaces in JDOM trees changed and became less
> convenient and flexible.
> I have documents like this:
> <html xmlns="">
>  <table>
>    <tr>
>      <td>page</td>
>      <td>type</td>
>      <td>comment</td>
>    </tr>
>    <tr>
>      <td><a href="/Home"/></td>
>      <td>conf</td>
>      <td>Home Page</td>
>    </tr>
>    <tr>
>      <td><a href="/ToolBar"/></td>
>      <td>conf</td>
>      <td>Tool Bar</td>
>    </tr>
>  </table>
> </html>
> The namespace of the root element is variable and might be the XHTML
> namespace, another namespace, or no namespace at all. The table
> structure is always the same, and cell values vary. And I have some
> code that executes the following query:
> SAXBuilder sax = new SAXBuilder();
> Document doc = StringReader(...);
> Element rootElement = doc.getRootElement();
> JXPathContext ctx = JXPathUtil.newContext(rootElement);
> String value = ctx.getValue("/table/tr[2]/td[2]");
> This worked fine with JXPath 1.1, but it doesn't work anymore with
> 1.2. The new JXPath version throws an exception:
> org.apache.commons.jxpath.JXPathException: No value for xpath:
> /table/tr[2]/td[2]
> at 
> org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue(
> at 
> org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue(
> Why would this not work, considering that all the DOM nodes live in
> the same namespace - the namespace of the context bean (root element)?
> It appears that I can register the XHTML namespace, but then I have to
> use a prefix for every element name in my query - and it won't work if
> the namespace is not set or is different (that's possible in my app).
> Is there a solution to this problem, i.e. is there a way to make
> JXPath interpret the root element's namespace as the default namespace
> requiring no prefix in XPath queries?
> Thanks in advance,
> -Michael
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message