I do a combination now. I enabled the Invoker and put a mapping in the web.xml for it. I use the RequestDispatcher to forward to the other servlets via the invoker. I enabled the reloading feature of the context. And everything works as I need it.
mfg Michael Nitschke -----Original Message----- From: QM [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 5:17 PM To: Tomcat Users List Subject: Re: RequestDispatcher resource not available : The point is I won't be able to start the server frequently to add new : servlets, because our company needs the service 24/7. Understood; please report your final solution, if possible. Whenever an app steps out of the standard, there's an opportunity for innovation. =) One other idea: Tomcat clustering? e.g. reload Container1 while Container2 continues to serve requests, then reload Container2 when Container1 comes back up? (Of course, this works only for changes to the servlet mappings; changes to lower-level code libraries would require actual downtime.) I had a similar setup w/ Weblogic a couple of years ago, also in a 24x7 shop. Being able to take down one member of the cluster in midday was quite a treat. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- 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]
