cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <>
Subject Re: WASD 4.0.3
Date Wed, 30 Apr 2003 18:19:02 GMT
I think that if core.log is finding his jar, it's in WEB-INF/lib.


At 02:13 PM 4/30/2003, you wrote:
>I haven't worked with WASD, but I just spent a lot of time working out 
>classloader issues in WAS 4.0.x, so maybe my experiences will shed some light.
>In WebSphere 4, there are 4 built in "visibility" modes.  In addition, 
>they added a new one called J2EE Application Visibility which must be 
>specified as a system property on the JVM settings of the Application 
>Server.  I found a lot of good info on IBM's site, hunt around for 
>information on "module visibility".  In addition, this article may help: 
>Looking at your e-mail, I think putting the JAR on your WSAD classpath is 
>the wrong approach.  You need to get it into the classloader that loads 
>your Cocoon WAR.  Maybe even try WEB-INF/lib or making an EAR and using 
>manifest classpaths.
>Ryan Hoegg
>ISIS Networks
>gon ishihara wrote:
>>I am getting an error in Access.log saying "No
>>suitable driver found".  But in the core.log, the jar
>>file which contains the driver (jt400.jar) is listed
>>as a part of class path.
>>Here is the access.log's trace.
>>Thank you for taking your time ;)
>>ERROR   (2003-04-30) 10:37.06:873   [access]
>>Servlet.Engine.Transports:10/CocoonServlet: Problem
>>with Cocoon servlet
>>org.apache.cocoon.ProcessingException: Exception in
>>java.lang.RuntimeException: Could not get the
>>datasource java.sql.SQLException: No suitable driver
>>         at
>>--- Geoff Howard <> wrote:
>>>I have no experience with WASD but what do your
>>>logs say with respect to the datasource.  Try
>>>through them for your datasource name.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message