No, there is no Apache in my situation. I guess I will begin playing
with ROOT application.
-Original Message-
From: Maximilian Stocker [mailto:m...@talentoyster.com]
Sent: Tuesday, October 26, 2010 4:20 PM
To: 'Tomcat Users List'
Subject: RE: Re: deploying as ROOT applicatio
On Tue, Oct 26, 2010 at 1:12 PM, Aggarwal, Ajay
wrote:
> In that case, you are right, making my application as ROOT is a better
> alternative. Just that I haven't been able to locate official Tomcat
> documentation on deploying as ROOT application. And I didn't want to enter an
> un-supported
bject: RE: Re: deploying as ROOT application
Well, I was assuming these filters are global to Tomcat instance and not
specific to an application. I haven't looked at available implementations of
these filters yet. Based on your response I take it that my assumption is wrong.
In that cas
Well, I was assuming these filters are global to Tomcat instance and not
specific to an application. I haven't looked at available implementations of
these filters yet. Based on your response I take it that my assumption is wrong.
In that case, you are right, making my application as ROOT is a b
On Tue, Oct 26, 2010 at 12:52 PM, Aggarwal, Ajay
wrote:
> But now I am thinking that perhaps URL rewriting can help me here.
> Perhaps I can still deploy my application as "myapp" and use URL
> rewriting filters to do following mapping:
>
> /foo --> /myapp/foo
> /bar --> /myapp/bar
> /sample1.
Perhaps I can discuss my needs here with other forum members. The only
reason I thought my app needs to be a ROOT application is because I need
to serve following contexts from my application:
/foo/*
/bar/*
/sample1.html
But now I am thinking that perhaps URL rewriting can help me here.
Per
