You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by manuel aldana <al...@gmx.de> on 2009/03/01 21:45:35 UTC
how to realize subdomain app areas?
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
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by Markus Joschko <ma...@gmail.com>.
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
<th...@gmail.com> wrote:
> Em Sun, 01 Mar 2009 17:45:35 -0300, manuel aldana <al...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Sun, 01 Mar 2009 17:45:35 -0300, manuel aldana <al...@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by Norman Franke <no...@myasd.com>.
When I needed something like this, I wrote a servlet filter. I wasn't
using Apache, just Tomcat, so no mods. I also wanted everything in the
same application, so virtual hosting was out. The servlet filter gets
the HttpServletRequest.getHeader("host") and then redirects to a URL
in my application (via a RequestDispatcher). Short and sweet.
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Mar 1, 2009, at 4:21 PM, Ulrich Stärk wrote:
> I think you could do this with Apache and mod_jk in front of your
> tomcat server. You could forward requests going to the virtual host
> cs.your.domain.com to your.tomcat.host:port/some/path and requests
> to login.your.domain.com to your.tomcat.host:port/other/path
>
> HTH,
>
> Uli
>
> manuel aldana schrieb:
>> 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
>>>> aldana@gmx.de
>>>> software-engineering blog: http://www.aldana-online.de
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>> -----
>>>> manuel aldana
>>>> aldana((at))gmx.de
>>>> software-engineering blog: http://www.aldana-online.de
>>>>
>>>>
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by manuel aldana <al...@gmx.de>.
got it. thanks.
you're right, makes more sense as twiddling around on the Servlet side.
Ulrich Stärk schrieb:
> I think you could do this with Apache and mod_jk in front of your
> tomcat server. You could forward requests going to the virtual host
> cs.your.domain.com to your.tomcat.host:port/some/path and requests to
> login.your.domain.com to your.tomcat.host:port/other/path
>
> HTH,
>
> Uli
>
> manuel aldana schrieb:
>> 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
>>>> aldana@gmx.de
>>>> software-engineering blog: http://www.aldana-online.de
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>> -----
>>>> manuel aldana
>>>> aldana((at))gmx.de
>>>> software-engineering blog: http://www.aldana-online.de
>>>>
>>>>
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
--
manuel aldana
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by Ulrich Stärk <ul...@spielviel.de>.
I think you could do this with Apache and mod_jk in front of your tomcat server. You could forward
requests going to the virtual host cs.your.domain.com to your.tomcat.host:port/some/path and
requests to login.your.domain.com to your.tomcat.host:port/other/path
HTH,
Uli
manuel aldana schrieb:
> 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
>>> aldana@gmx.de
>>> software-engineering blog: http://www.aldana-online.de
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>> -----
>>> manuel aldana
>>> aldana((at))gmx.de
>>> software-engineering blog: http://www.aldana-online.de
>>>
>>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by manuel aldana <al...@gmx.de>.
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
>> aldana@gmx.de
>> software-engineering blog: http://www.aldana-online.de
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>> -----
>> manuel aldana
>> aldana((at))gmx.de
>> software-engineering blog: http://www.aldana-online.de
>>
>>
>
>
--
manuel aldana
aldana@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: how to realize subdomain app areas?
Posted by Markus Lux <ma...@gmail.com>.
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
> aldana@gmx.de
> software-engineering blog: http://www.aldana-online.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org