Hi, that wouldn't be relevant to tapestry. You should configure that in your webserver which forwards all your requests to the servlet container running your tapestry application. Different subdomains will lead to different entry points in your application.
aldana wrote: > > hi, > > 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) > > How is it possible to map these different entry points in one tapestry > web-application? > > -- > manuel aldana > ald...@gmx.de > software-engineering blog: http://www.aldana-online.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > ----- > manuel aldana > aldana((at))gmx.de > software-engineering blog: http://www.aldana-online.de > -- View this message in context: http://www.nabble.com/how-to-realize-subdomain-app-areas--tp22277748p22277885.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
