I'm actually well aware of how the wrapper.classpath works vs. the servlet
path - what I don't understand is where Turbine is supposed to live - I am
assuming it goes in the wrapper.classpath, since it needs to be loaded
before ApacheJServ.jar - but the Install docs are not too clear on this:
the jyve document says it goes in the servlet classpath, while the turbine
one says to put it in the wrapper.classpath.
Anyways, I've tried it both ways and I still get the same errors. I'm
also getting a mysql error still, even with the proper account name and
database name.
On Tue, 8 Feb 2000, jon * wrote:
> on 2/8/00 4:21 PM, Brett Carter <[EMAIL PROTECTED]> wrote:
>
> > Ok, ok, so i switched back to mm.mysql.jdbc-1.2b - but now when I log in,
> > I just get a blank document - and now I get the following in the log.
> > Also - is the turbine.jar supposed to be in the wrapper.classpath and the
> > servlet path?
> > -Brett
> >
> > [08/02/2000 16:13:29:129 PST] java.lang.NoClassDefFoundError:
> > org/apache/turbine/util/TurbineUserPeer
>
> Please go read the FAQ's and/or archives of this list about how the two
> different classloaders work. I have repeated it over and over again and I'm
> tired of re-typing it.
>
> -jon
>
> --
> Come to the first official Apache Software Foundation
> Conference! <http://ApacheCon.Com/>
>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]