yeah, but the requests should go to the same webapplication (port should
always be 80), so I somehow need to configure this inside my one
tapestry app.
Markus Lux schrieb:
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
--
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
