hmmm, I don't think Engine worksaccording to
http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html
Exactly one *Engine* element MUST be nested inside a
Servicehttp://tomcat.apache.org/tomcat-5.5-doc/config/service.htmlelement
I need twoone for requests .domain1.com and one for
From: Dean Hiller [mailto:dean.hil...@gmail.com]
Subject: Re: RemoteHostValve for infinite domains? Patch submit
question...
http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html
Exactly one *Engine* element MUST be nested inside a
Servicehttp://tomcat.apache.org/tomcat-5.5-
doc
Dean Hiller wrote:
...
I need twoone for requests .domain1.com and one for
.domain2.com where is infinite combination.
I think that you are right. Based on the little I know about Java and
Tomcat and RequestDispatcher, I would suggest a range of possible
solutions, in my
yes, I have thought through all those actually. Was just talking about
urlrewrite filter and apache this morning. Issue with that then is having
to keep their company name in a param of every single redirect seam does
which is not the easiest of things to dothat way, company could be put
in
On Thu, Apr 1, 2010 at 9:45 AM, Dean Hiller dean.hil...@gmail.com wrote:
I like the ip idea(except for needing two tomcats).
You don't need 2 tomcats; a connector can be told to listen on a
specific IP...
Two services in tomcat doesn't work as then we would need different ports
which is
yes, interesting, unfortunately, I am running our QA and customer demo
machine behind comcast at home so there is only one ip, though it would work
for our production environment.
Dean
On Thu, Apr 1, 2010 at 10:56 AM, Hassan Schroeder
hassan.schroe...@gmail.com wrote:
On Thu, Apr 1, 2010 at
On Thu, Apr 1, 2010 at 10:00 AM, Dean Hiller dean.hil...@gmail.com wrote:
yes, interesting, unfortunately, I am running our QA and customer demo
machine behind comcast at home so there is only one ip, though it would work
for our production environment.
Then you could use the same 2-Engine
