Jon, Using the ServletContextListener#contextInitialized method is "where" I was going to do it, I use the same procedure to initialize other things as well, my question was "how". What is it you are calling in OJB to do the initialization? Is there some magic method to tell OJB to initialize? Code snippet perhaps?
Thanks much, Rick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 19, 2005 12:06 PM Posted To: OJB Dev Conversation: Proper OJB Startup Procedure? Subject: Re: Proper OJB Startup Procedure? I initialize OJB in a ServletContextListener#contextInitialized method. This guarantees that OJB is initialized when the web application in loaded into the container. It has the downside of increasing container start-up time. Jon French Programmer ECOS Development Team [EMAIL PROTECTED] 970-226-9290 "Rick G" <[EMAIL PROTECTED]> 10/19/2005 12:43 PM Please respond to "OJB Users List" <[email protected]> To "'OJB Users List'" <[email protected]> cc Subject Proper OJB Startup Procedure? Is there a preferred way to initialized OJB when starting a web app? Currently, on my system, OJB doesn't really load up until the first DB related call. Was wondering if there were some call I could make to an OJB Factory class or whatever, to initialize OJB, other than making a call that would invoke a query. On a side note, is there a way to pragmatically get the configured OJB Cache setting? Other than reading it out of the repository_database.xml file of course. Thanks for any tips/suggestions, Rick Gavin --------------------------------------------------------------------- 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]
