It is actually quite a common deployment strategy. You have Apache httpd server in front of Tomcat. The httpd server serves several domains/hostnames. In this case 6. Each domain has a set of uri rewrite rules that prefixes the uri with the context path and passes the request on through the connector. So for instance on my site
www.fashioncontent.com/Login.htm becomes /fc-portal/Login.htm when it reaches Tomcat. If I deployed as root I would be forced to have 6 instances of Tomcat running on the server. Henrik "Kent Tong" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] > hv <at> Fashion Content <info <at> fashioncontent.com> writes: > >> <contribution configuration-id="tapestry.InfrastructureOverrides"> >> <property name="contextPath" value=""/> >> </contribution> >> >> Doesn't seem to have any effect though. Links still include the context >> path. >> >> I wonder why??? > > It won't work because the Infrastructure class has a getContextPath() > method. The properties added this way are consulted only when it > doesn't have a real Java property of the same name. > > However, why would you like to set the context path to empty? This > will break lots of stuff. Why not just deploy your app as ROOT? > > -- > Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) > > > --------------------------------------------------------------------- > 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]
