Hmm, quite an interesting suggestion. But since I have a working solution in
T3, I think I will just stick to making the T4 version work the same way.
Since tapestry is so cleanly designed, patching the contextPath is actually
quite a simple matter.
Henrik
----- Original Message -----
From: "Kent Tong" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.java.tapestry.user
Sent: Sunday, November 20, 2005 1:19 PM
Subject: Re: How do you set a property of service after construction
hv <at> Fashion Content <info <at> fashioncontent.com> writes:
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.
Have you tried a mapping that keeps the context path like:
www.fashioncontent.com/Login.htm =>
internal.fashioncontent.com:80/Login.htm
www.foo.com/Login.htm =>
internal.foo.com:81/Login.htm
Then configure Tomcat like:
<Server ...>
<Service ...>
<Connector port="80" proxyName="www.fashioncontent.com" proxyPort="80"/>
...
</Service>
<Service ...>
<Connector port="81" proxyName="www.foo.com" proxyPort="80"/>
...
</Service>
</Server>
In each engine host, deploy your app in the ROOT context. This is
still just one instance of Tomcat.
---------------------------------------------------------------------
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]
