> -----Original Message-----
> From: jean-frederic clere
> >
> OPT=-Djava.class.path=${TOMCAT_HOME}\bin\tomcat-jni.jar;${TOMCAT_HOME}
> > \s
> > erver\lib\commons-logging.jar
>
> I do not like this work-around: we will have end with a huge
> classpath.
>
Neither do I, but this is the only way for now to be able to use the JNI
at all. If the JkMain or TomcatStarter loads the commons-logging at
first place we wouldn't have this problem.
I've added the LogFactory to the AprImpl that reports the error on TC
startup from inprocess and fails to start if the commons-logging is
missing, cause JNI wouldn't work properly at the first place without it.
So, fixing classloader is a showstopper on any jk2 release, and as I
said it is only a workaround that will disappear once that is fixed.
MT.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
