On Sat, 8 Jun 2002, Mladen Turk wrote: > Are there any reason why are we loading jkjni, or mod_jk2 for inprocess > mode. > I think that the same can be accomplished using JNI RegisterNatives. > Further more you can build the mod_jk as static module then. > It would IMO require and some minor java refactoring just to know when > to load the jkjni calling AprImpl.jniMode().
jkjni is for java standalone. The only reason we load mod_jk2.so for inprocess is that nobody wrote the RegisterNative code yet :-) ( it was easier to just load mod_jk2 ). > I've tested the concept and it works perfectly withouth the need to > specify the nativeSo in config. +1 ! Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
