Wrap the service in a ServletContextListener. The Servlet2.3 spec and higher mandate that these listeners be invoked before the application can process requests; so initialization can take place here and they have access to the application init parameters through web.xml. Then place them in ServletContext for application wide access.
robert > -----Original Message----- > From: Kommineni, Sateesh (GE Consumer & Industrial) > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 25, 2004 7:21 AM > To: [EMAIL PROTECTED] > Subject: Common Services across Different Actions. > Importance: High > > > > Hi All, > > In our Application we have identified few common Services which we are planning > to develop as reusable components. > > The approaches we identified are > > 1) Representing each service as a Plug-in so that we can initialize all the > Service when the Web App is initialized . > > 2) Create a BaseAction and have all the resources available in that Action class . > Sub Class all your Custom Actions > from the BaseAction. > > Is there any Other Approach that we are missing here > > Thanks a lot > Sateesh > > --------------------------------------------------------------------- > 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]
