<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Hi</div><div><br></div><div>If you pull the JDOM code from github, set it up as an eclipse project (if you use eclipse...), then right-click the build.xml file and run the eclipse target. If you use eclipse you can then right-click the project and run all tests, or you can run the ant junit target.</div><div><br></div><div>As for which DOM you use, run your project with the java option -Djaxp.debug=1 to see which DOM is found.</div><div><br></div><div><div style="font-size:75%;color:#575757"><br>Rolf<br></div></div> <br>Larsen <larsen007@web.de> wrote:<br>Hi Rolf,<br><br>I haven´t used unit tests so far and would need some instructions on how <br>to run them in case this becomes necessary.<br><br>How can I check for a buggy DOM implementation?<br><br><br>Lars<br><br><br>On Wed, 07 Nov 2012 19:31:09 +0100, Rolf Lear <jdom@tuis.net> wrote:<br><br>> Hi (again).<br>><br>> Based on some double-checking, I suspect that you have a buggy DOM <br>> implementation?<br>><br>> GetTextContent returns nodeBalue for Text nodes... Node.getTextContent <br>> says it should anyway.<br>><br>> I will check it out some more later.<br>><br>><br>><br>> Rolf<br>> Larsen <larsen007@web.de> wrote:> I am quite a JDOM2 newbie and noticed <br>> strange/incorrect behaviour when<br>>> converting a W3C-Element to a JDOM-Element. (snip)<br>><br>><br>> PS: Using latest JDOM 2.0.3 and Java 7 ("1.7.0_09")<br>> _______________________________________________<br>> To control your jdom-interest membership:<br>> http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com<br><br>_______________________________________________<br>To control your jdom-interest membership:<br>http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com</body>