Hi Terry
 
I've just built the whole dom4j code base and ran all the JUnit tests on JDK 1.2.2, JDK 1.3.1 and JDK1.4 with no problem whatsoever. So I don't think there is any problem with JDK1.2 support of dom4j. Sounds like a container problem - maybe a W3C DOM version clash maybe?
 
James
----- Original Message -----
Sent: Wednesday, March 27, 2002 4:46 AM
Subject: [dom4j-user] JDK 1.3 Dependency?

Hi All,

(I'm having a heck of a time getting this message accepted by the
listserver, so I apologize in advance if more than one copy is sent out.)

I'm a dom4j newbie and have been pulling my hair out trying to get dom4j
working with JTidy.  The JTidyDemo works just fine, but when I copied the
two lines of code I needed into my code, and ran the resultant module under
Tomcat (3.2.2), I got the strangest error behavior.  It was as if there was
an invisible exception that I couldn't catch directly.

I went to the list's archives and stumbled across a message of July 12, 1999
from Minal Ashar, apparently having a similar problem.  A response dated
October 15, 2001 (???) stated there was a JDK 1.3 dependency but that it had
been fixed.

Well, it turns out that Tomcat was using JDK 1.2.2, so I switched to 1.3.1
and it worked fine!  I'm using (I think - I just downloaded it several days
ago) the latest dom4j (patched-1.3) and JTidy (04Aug2000r7).

Does this mean I always *must* use JDK 1.3+ with dom4j?  If so, is there an
earlier release without this dependency?

Regards,

Terry Steichen

Reply via email to