On Mon, 11 Sep 2000, Gopal Ramasammy-Cook wrote:
> Hi Jon
>
> Thanks for the response. However, I do have Turbine as a set of classes (which I
>myself compiled) in my webapps/Web-INF/classes directory. I do not think it is a
>Turbine class path issue, for it was, the Turbine class itself would not found. The
>reason I have used the Turbine classes as opposed to the Turbine jar, is so that I
>can debug easier (and understand Turbine better as well).
>
> As I mentioned previously, I have actually placed a System.out.println() debug
>statement in my TurbineServices class, and this print statement actually does appear
>in my Tomcat console, which means that the Turbine classes are being found by the JVM.
>
> The problem appears to be specifically around the Global Cache Service. When I
>remove the code that actually calls the cache service, my code runs correctly.
>
> By the way, I am using the snapshot of 28 Aug 2000.
>
> I hope this helps explain my error further.
I believe the problem is in BaseInitableBroker.java:223 wher
it goes
try
{
initable = (Initable)Class.forName(className).newInstance();
}
The Class.forName is failing as it checks context
classloader and is not finding appropriate classes.
This is prolly because your classes are in WEB-INF/lib and
the turbine classes are in WEB-INF/classes or vice versa. It
always leaves me pulling out hair when that sort of thing
happens. Easieest solution is to unjar everything into
WEB-INF/classes - thou you may want to package it up
propperly when you release it as putting heaps in
WEB-INF/classes can cause odd behaviour.
Cheers,
Pete
*--------------------------------------------------*
| Latrobe University, | Does the name 'Pavlov' |
| Bundoora, Australia | ring a bell ? |
*--------------------------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
