This is actually a webapp question. If you copy the cocoon.war file to another name, say test.war, you can access it from that name, /test here.
I just copy the original Cocoon.war file to another name, let tomcat unpack it to the new directory and then erase everything I don't need. The configuration in Tomcat makes sure only the right sites can access their own webapp and not the other. Bert At 14:54 14/01/2002 -0700, you wrote: > From the FAQ it would seem that one cannot run Cocoon from a URL or >context other the /cocoon (since the FAQ only offers ideas for changing >the URL by having Apache rewrite on the fly.) Is this correct (if so, >anyone have any guesstimates on how much work would be involved in >changing or removing this)? > >Thanks, > >Yuri Gadow > > > > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.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/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
