I'm not sure how useful this answer is as it doesn't fit very well with the idea that mulpile sites are hosted in a single webapp ideology that cocoon follows (at least thats my understanding). But separting your sites into seperate webapps will allow you to have your sites run in separate jvms, in fact as separate users (thats what i do to allow each user to start and stop his/her jvm).
The downside to this is that you'll need all the cocoon dependencies in each webapp's lib directory (unless the classloader of the container you use can load from a more central place) and you cant share config resources between sites (I'd say this was better design anyway). The advantage is that you don't into trouble when you stop and start apps, also if one servlet (cocoon servlet) this doesn't mean all your sites die. Alernatively you can have all your cocoon apps running in one jvm and perhaps reload individual apps (tomcat manager for example), but I wouldn't recommend this as if the app dies during reload all your apps will (out of memory errors etc). Mark On Fri, 11 Mar 2005 21:28:23 +0100, Yves Vindevogel <[EMAIL PROTECTED]> wrote: > That's the same result ... all clients out for just a moment ... > > On 11 Mar 2005, at 21:06, Petko Petkov wrote: > > > I belive that you can restart just cocoon. > > > > Good luck! > > > > --------------------------------------------------------------------- > > 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]
