News...
Since creating this problem I've deployed an older app ( which doesn't
use iBatis) to the same env and it works perfectly well with my
DataSource. Therefore the problem must lie in the iBatis config
somewhere
Has anyone else experienced difficulties migrating to WAS 6 ( 6.0.2.3
to
fine under Tomcat 5.5, but WAS
6.0 got ClassNotFound exception.
Nathan
-Original Message-
From: Paul Carr [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 8:42 AM
To: user-java@ibatis.apache.org
Subject: RE: Migr WAS 5.0-6.0
News...
Since creating this problem I've deployed
messages
-Original Message-
From: Nathan Ward [mailto:[EMAIL PROTECTED]
Sent: 06 November 2006 13:58
To: user-java@ibatis.apache.org
Subject: RE: Migr WAS 5.0-6.0
WAS 6.0 uses JDK 1.4 doesn't it? Does iBATIS require JDK 1.5? I doubt
it,
but thought I'd mention it.
I attended a NFJS
, 2006 7:39 PM
To: user-java@ibatis.apache.org
Subject: RE: Migr WAS 5.0-6.0
Hi Nathan,
I was running fine on WAS 5.0 with JDK 1.3.1, so I doubt it's
a JDK issue. When I started trying to move to WAS 6.0 I had some naming
difficulties ... my sqlmapconfig had java:comp in the JNDI names
, November 06, 2006 7:39 PM
To: user-java@ibatis.apache.org
Subject: RE: Migr WAS 5.0-6.0
Hi Nathan,
I was running fine on WAS 5.0 with JDK 1.3.1, so I doubt it's
a JDK issue. When I started trying to move to WAS 6.0 I had some naming
difficulties ... my sqlmapconfig had java:comp
November 2006 13:58To: user-java@ibatis.apache.orgSubject: RE: Migr WAS 5.0-6.0WAS 6.0 uses JDK 1.4 doesn't it? Does iBATIS require JDK
1.5? I doubtit,but thought I'd mention it.I attended a NFJS conference that past weekend where Ted Neward saidthatWAS has a very complicated classloader structure. I
@ibatis.apache.org
Subject: Re: Migr WAS 5.0-6.0
iBATIS works fine on WAS 6.0. There is some information on this
WIKI page about configuring iBATIS in different WAS scenarios:
http://opensource.atlassian.com/confluence/oss/display/IBATIS/Environment+Specific+Information
Jeff
