I also agree that this should be handled by a virtual host setting in either the webserver in front or the servlet container the app is running in. However if you have a wildcard in your DNS settings and all subdomains point to the same destination which is the server your tapestry is running in, you might get away with a tapestry Requestdispatcher that checks your request URL and then redirects accordingly within your application.
However this is kind of reinventing the wheel. Regards, Markus On Sun, Mar 1, 2009 at 10:24 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Sun, 01 Mar 2009 17:45:35 -0300, manuel aldana <ald...@gmx.de> escreveu: > >> I want to structure app-areas by subdomain: >> http://www.xxx.com/ (public area) >> https://login.xxx.com/ (non-public area for customers) >> https://cs.xxx.com/ (non-public internal area) > > This looks like virtual hosts to me. This isn't a Tapestry issue, it's a > servlet container one and each one has it own way to do that. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > Consultor, desenvolvedor e instrutor em Java > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
