1. rename tomcat/webapps/cocoon to tomcat/webapps/lgic
then use http://host.org/lgic/lgic instead of http://host.org/cocoon/lgic
2. change the way the top level sitemap mounts your lgic sitemap so that
its accessed via "lgic" instead of "lgic/lgic" e.g.
<map:match pattern="**">
<map:mount check-reload="no" src="lgic/" uri-prefix=""/>
</map:match>
Also read the tomcat docs on tomcat/conf/server.xml - the servlet context
part of the URL doesn't have to match the name of the directory under
tomcat/webapps - thats just the default behaviour. You can use this instead
of 1. above.
-----Original Message-----
From: Lars Huttar [mailto:[EMAIL PROTECTED]
Sent: Monday, 31 May 2004 9:33 AM
To: Cocoon Users List (E-mail)
Subject: not requiring "cocoon/" in URLs?
Hi all,
We have a requirement (or a preference at least) not to require
"cocoon/" in our URLs. I.e. we'd like a user to be able to go to the URL
"http://host.org/lgic"; instead of "http://host.org/cocoon/lgic";.
I see that we can get this behavior if we run Cocoon under Jetty;
but we're currently running it under Tomcat, with several different
applications being used by different people, and I'm wondering if
moving to Jetty will break things. Is Jetty very different from Tomcat?
On what basis would you choose to run Cocoon under one or the other?
Alternatively, is there a way to configure Tomcat, or Cocoon, to
not require "cocoon" in the URL?
Thanks,
Lars
---------------------------------------------------------------------
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]
