for those who are investigating the matter, here is how far I got with debugging: without extending TurbineUser : Turbine init() is called EVERY TIME tomcat is stopped and then started then a singleton class:TurbineServices is called with getInstance() and then in the init() of Turbine, initPrimaryServices(config) of it is called ensuring that the configuration ( BaseConfiguration()) of the extended BaseServiceBroker class is mapped
what happens when extending TurbineUser is that the init() of Turbine class is called every other time and therefore NO CONFIGURATION mapping and a NPE( in tomcat) logs when trying to load the services from the properties file Akmal ----- Original Message ----- From: "oron ogdan" <[EMAIL PROTECTED]> To: "'Turbine Users List'" <[EMAIL PROTECTED]> Sent: Thursday, August 21, 2003 12:27 AM Subject: RE: extended user class not found problem > Just finished migrating from 2.2 to 2.3 RC1 successfully > take a look at the 2.3 documents for the new TorqueSecurityService. > > while not trivial to migrate, it does solve the ExtendedUser not found > problem > good information on these emails from the developers list as well > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg12645.html > http://www.mail-archive.com/[EMAIL PROTECTED]/msg12663.html > > Oron > > -----Original Message----- > From: Scott Eade [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 20, 2003 3:43 PM > To: Turbine Users List > Subject: Re: extended user class not found problem > > > Henning P. Schmiedehausen wrote: > > >Michal Frackowiak <[EMAIL PROTECTED]> writes: > > > > > >>I have a diffrent entry in Tomcat's logs. just after a tomcat is > >>started, my app throws an error. what helps is reloading app using the > >>manager application. but when I start tomcat and try to use my app I get > >>an entry in logs: > >> > >> > > > >Do you really need session persistence over container restarts? If not, > >configure your container to not save the sessions. > > > > > While I haven't checked the latest tomcat release, certainly up to now > the mechanism provided to stop the sessions from being persisted across > a context reload/container restart does not in fact work. > > I have made the script I use to start tomcat delete the persisted session > file. If it is a system that I alone am testing the problem usually does > not occur if I logout before I reload the context manually - if you auto > reload then you are probably going to have to restart manually in order > to clear the persisted sessions (as suggested by Michal). > > It would be great to eventually track down the culprit. > > Scott > > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
