So the code breaks in one context and works fine in another. When I run into
problems of that class involving XML parsing I always look for threading
issues. Most Java XML technologies rely on underlying parsers which, for
reasons of performance, ignore thread safety. Is it possible that some ot
I always do a startTransaction() in setUp() and an endTransaction() in
tearDown(). That way I don't leak connections.
Jim
-Original Message-
From: Oscar Picasso [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 01, 2005 7:51 AM
To: user-java@ibatis.apache.org
Subject: Ibatis and Junit
Looks like a classloader issue. You probably have a newer or older
version of that class in a jar file somewhere. And no, renaming jars
will make no difference. I'd recommend you start by hitting jarhoo:
www.jarhoo.com, which will tell you in what jar files certain classes
are commonly found.
If