tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bxqdev <bxq...@themailbay.com>
Subject Re: Different webapp paths on different hosts
Date Sat, 02 Feb 2013 19:36:34 GMT


On 1/28/2013 7:13 PM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> bxqdev,
>
> On 1/26/13 1:09 AM, bxqdev wrote:
>>
>>
>> On 1/26/2013 1:05 AM, Christopher Schultz wrote: Dude,
>>
>> On 1/25/13 12:38 AM, bxqdev wrote:
>>>>> i want to have one instance of webapp,
>>
>> No problem.
>>
>>>>> which has two paths,
>>
>> Problem: one context = one path = one instance
>>
>> If you want two separate paths, you need two separate contexts.
>>
>>>>> and each of the paths serves the root of different domains
>>
>> That just doesn't make any sense. The root of a domain is, by
>> definition, "/" (contextPath=""), so there aren't any other paths
>> to consider.
>>
>>> looks like the goal is not reachable with plain tomcat
>>> configuration.
>>
>>
>>>>> once again: * one webapp * has 2 different paths: "/path1"
>>>>> and "/path2" * served on 2 domains * when user goes to
>>>>> http://path1.com/ -> {webapp}/path1 is served as root path *
>>>>> when user goes to http://path2.com/ -> {webapp}/path2 is
>>>>> served as root path
>>>>>
>>>>> is it possible?
>>
>> What you are saying is nonsensical (specifically, the part where
>> you say that you want /path1 to be mapped to "root".
>>
>> If you want two virtual hosts, then define two virtual hosts. If
>> you want an app on each host configured as ROOT, then make your
>> two virtual hosts have two separate appBase directories (which
>> should be a requirement in the first place of two virtual hosts)
>> and toss a copy of your WAR file in each appBase, both named
>> ROOT.war (cApITaLS matter).
>>
>> You can't deploy a single copy (in memory) of your webapp and
>> expect to get all your requirements above met. If you want to have
>> a single WAR file on the disk and deploy it multiple times, you
>> *can* do that but I'm not sure why anyone would want to.
>>
>>> looks like the goal is not reachable with plain tomcat
>>> configuration.
>
> I seriously don't understand your "goal" or your "problem". It sounds
> like you want two separate webapps smashed into a single context where
> one webapp gets served by one domain and another webapps gets served
> by the other domain. I don't know why you don't just split them up
> into two separate webapps just like $DIETY intended.

if that was the solution, i wouldn't ask the question in the first place.

>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEAREIAAYFAlEGlY0ACgkQ9CaO5/Lv0PD86wCfcid6tNjOzzR0BJZh2tF5672y
> 09kAmwQ/o+S3jP3Ii033Wfm1UkVmecXs
> =shqR
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message