Hi, I am using Jetspeed 1.5 with Tomcat 4.1.30 and JSDK 1.4.2_05. I have modified the jetspeed JetspeedSessionValidator which is a Turbine (2.2) action. This new action class is declared as sessionValidator in TurbineResource.properties (action.sessionvalidator=WolSessionValidator). I kept the standard (org.apache.jetspeed module). I develop and compile on Windows.
Everything works perfectly under Windows, but fails with Debian 3.0 (bf2.4) where I get an "action not found". Using -verbose:class, I checked that my class is in fact loaded by the JVM, so, it is found. Looking at Turbine source, I saw that the "action not found" exception is thrown whatever the underlying java reason could be. I turned log4.properties in debug mode, I can see that the AssemblerBrokerService is initialized (Finish Initializing service (late)) just before the failure. On Debian, everything works fine with the Jetspeed action class delivered in jetspeed1.5.jar. I try to deploy my action class containing exactly the same source as the Jetspeed one and got a failure. So the problem may be linked to compilers, or JDK, or debian, or a classCastException due to some jar hell. So, I am looking for help: -Does someone encountered the same kind of problems on Debian? -I don't see traces of some debug or info lines in my logs, even with log4j in debug mode. Is there something else to configure? For instance, I can't figure out which class is really loading my action class and when (I am not used to commons.logging). -And of course, If someone knows the solution... Tx in advance. Jean Fastr� VALORIS, Belgium.
