the only thing i have to do is to put cocoon-something.war into webapp directory and restart tomcat
now i have as many instances of cocoon i want i access them http://localhost:8080/cocoon/ http://loclahost:8080/cocoo-new/ .. .. thanks Kounis Stavros On Wed, 9 Oct 2002, Vadim Gritsenko wrote: > Barbara Post wrote: > > >Or use an unzipping tool to deploy/unzip the .war then copy the content > >where you want with any name you want for the containing folder. > >Then modify Tomcat's server.xml : add a new context path. > > > > Last step is not necessary. Just put cocoon-new.war into webapps, or > unzip into webapps/cocoon-new - either way, you will get second cocoon > deployed in http://localhost:port/cocoon-new/ > > Vadim > > > >Just my 2 cents ;-) > > > >----- Original Message ----- > >From: "Katzigas Dimitris" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Wednesday, October 02, 2002 1:09 PM > >Subject: Re: cocoon second instance > > > > > > > > > >>Ok got it. > >> > >>I think that tomcat creates a subdirectory under webapps/ by the name of > >> > >> > >the > > > > > >>war file that you deploy. > >>e.g. If you deploy the cocoon-new.war i think that it will create a > >>cocoon-new/ subdirectory under webapps/. > >>I haven't test it with cocoon but works with othes war files. > >> > >>Good Luck. > >> > >>Dimitris Katzigas. > >> > >>----- Original Message ----- > >>From: "Cocoon User" <[EMAIL PROTECTED]> > >>To: <[EMAIL PROTECTED]> > >>Sent: Wednesday, October 02, 2002 1:58 PM > >>Subject: Re: cocoon second instance > >> > >> > >> > >> > >>>yep but i dont want to touch my working installation (i can not modify > >>>something that work in production machine) > >>> > >>> > >>>On Wed, 2 Oct 2002, Katzigas Dimitris wrote: > >>> > >>> > >>> > >>>>Stavro > >>>> > >>>>Rename the 2.0.1rc installation directory from /webapps/cocoon to > >>>>/webapps/cocoon.old > >>>>then copy the new war file as it is in the webapps/ directory and > >>>> > >>>> > >>restart > >> > >> > >>>>Tomcat. > >>>>Your old cocoon instalation won't be damaged, but you can't use it > >>>> > >>>> > >>anymore > >> > >> > >>>>unless you rename again > >>>>the directory /webapps/cocoon.old to /webapps/cocoon. > >>>> > >>>>Dimitris Katzigas > >>>> > >>>> > >>>>----- Original Message ----- > >>>>From: "Cocoon User" <[EMAIL PROTECTED]> > >>>>To: <[EMAIL PROTECTED]> > >>>>Sent: Wednesday, October 02, 2002 1:45 PM > >>>>Subject: cocoon second instance > >>>> > >>>> > >>>> > >>>> > >>>>>hi folks > >>>>> > >>>>> > >>>>>i have cocoon 2.0.1rc working into omcats /web-app > >>>>> > >>>>>i want to test cocoon 2.0.3 binary distribution > >>>>>without to upgrade or cancel my old installation > >>>>> > >>>>> > >>>>>can i put cocoon's 2.0.3 cocoon.war into /web-app as cocoon_new.war > >>>>> > >>>>>and restart tomcat > >>>>> > >>>>>how will tomcat then deploy this .war > >>>>> > >>>>>is it possible tomcat overwrite my old (but working) cocoon > >>>>> > >>>>> > >>installation? > >> > >> > >>>>> > >>>>>thnx > >>>>> > >>>>>kounis stavros > >>>>> > >>>>> > > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
