John McNally wrote: >A problem calling Torque.init() without a valid configuration object >having been set and related to the abstract/static nature of the class. >Not sure how to solve, so passing it on for others to ponder. > >john mcnally
John McNally wrote: > > That is a damn good analysis of the problem. I would expect this > problem might occur with class reloading turned on as well, but I have > never experienced the problem. I wonder what is different about the two > cases. I will submit this analysis to turbine/torque list, if you do > not mind. [...] Ah !! this problem reminds me the one I'm currently having w/ my webapp but I didn't get the time to investigate the problem yet, I thought we were storing things stupidly in the session ! I'm using Turbine 2.2b1 and Tomcat 4.0.1 w/ class reloading turned on during development and I'm having a NoClassDefFound on the UserPeer each time it reloads the webapp or if I shutdown Tomcat cleanly (assuming I'm logged). The standard manager of Catalina is serializing the session and fails when it reloads the session, depending on the context, you got either a direct stacktrace in your browser (reload) or an internal server error from Catalina.(restart) (the catalina log gives full details about the error then). I never had a NPE though. Stephane -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
