Re: [dom4j-user] xpath problem

2009-04-16 Thread Ozakca, Muzaffer
(document); I think this will retrieve the first “meta” node. Muzaffer From: matt.rossner-pr...@sanofi-aventis.com [mailto:matt.rossner-pr...@sanofi-aventis.com] Sent: Thursday, April 16, 2009 11:35 AM To: dom4j-user@lists.sourceforge.net Subject: Re: [dom4j-user] xpath problem Well it’s an HTML

Re: [dom4j-user] xpath problem

2009-04-16 Thread Matt.Rossner-prest
p://www.w3.org/1999/xhtml"; lang="fr"> Thanks for your help From: Linus Kamb [mailto:li...@iris.washington.edu] Sent: jeudi 16 avril 2009 17:29 To: Rossner, Matt PH/FR/PREST Subject: Re: [dom4j-user] xpath problem namespace? matt.ross

Re: [dom4j-user] XPath problem

2007-08-10 Thread Ozakca, Muzaffer
I wish I was clever and did some research first. I found the answer in the list archives: I should have done: code --- Map map = new HashMap(); map.put("result", "http://www.w3.org/2001/sw/DataAccess/rf1/result";); XPath xpath = DocumentHelper.createXPath("//result:k0"); xpath.s

Re: [dom4j-user] XPath problem with *

2005-01-29 Thread Edwin Dankert
> 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, i

Re: [dom4j-user] XPath problem with *

2005-01-29 Thread David P. Nesbitt
Edwin, Thanks very much for your response. 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 t

Re: [dom4j-user] XPath problem with *

2005-01-29 Thread Edwin Dankert
I can see one problem with your XML and another problem with your XPath. The problem with your XML is caused by the '<' character used as XML content. > <= This is not well-formed XML, it should be: <= Did this throw an exception? The XPath is wrong because, it does first of all not specify

Re: [dom4j-user] xpath problem, a clue to the problem.

2001-12-11 Thread James Strachan
} nodes = list.selectNodes("ancestor::ol"); if ((nodes != null) && (nodes.size() > 0)) { continue; } } } - Original Message ----- From: "Robert J. Lebowitz" <[EMAIL PROTECTED]> To: "Brain, Jim" <[EMAIL PROTECT

Re: [dom4j-user] xpath problem, a clue to the problem.

2001-12-07 Thread Robert J. Lebowitz
Actually, after "fixing" the html, I still continue to have the problem of the null pointer exception. I can't figure out what is causing it. In the interim, I just wrapped the code that throws the exception with a try/catch clause and ignore the exception. I'm still a bit puzzled about how to

RE: [dom4j-user] xpath problem, a clue to the problem.

2001-12-07 Thread Brain, Jim
In HTML, you should never have two ul's together, I think it should be: However, that