> The XML is already as you stated it needed to be (i.e. > it uses '<' rather than '<'). Since the XPath > expression is not part of an XML document (e.g. an XSL > Stylesheet), I don't believe that it needs to be > escaped in the String that is the parameter to the > XPath constructor. In fact, it does not work if it is > escaped.
I'm sorry that seems to be a problem with GMail... You're right, this seems to depend on the way the XPath is processed (they should really be interchangeable). > I did make the change to the program to include the > first xqx:expr prior to the '*' and the program runs > successfully. Thanks for that advice. > > However, I have a follow-up question. Why is the > first xqx:expr needed in the XPath expression? > Shouldn't the '*' match the first xqx:expr and its > descendents? I am very confused by this. Doesn't > this seem like a bug in DOM4J's XPath expression > evaluation? '*' is used to match all child elements of the current node, you could however have used '//' to match all descendants. So you could write your xpath like this: /rr:ReportRequest//xqx:[EMAIL PROTECTED]:type ... Hope this helped, Edwin ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ dom4j-user mailing list dom4j-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dom4j-user
