Sean
Wouldn't it be easier to have ONE webapp and determine the database
from, for example, the URL its invoked with?
Its a little difficult to know exactly how you are doing things but
instead of having /ctx1 /ctx2 /ctx3 and mapping each one to ctx1.war
why not have a filter in your setup which determines that its invoked
with /ctx1 and passes a parameter to the actual servlet which selects
the database you require? You could have one web app as ROOT and do it
that way.
Maybe you could explain further why you need 200 separate versions where
the only difference is the name of the database?
Regards
Alan Chaney
Sean W wrote:
Greetings!
I have a single war packaged application that needs to have about 200 unique
context paths running (200 copies of the application running - each uses a
different database based on the context name).
I know how to deploy 1 context at a time, but how can I do this so that if I
want to update all these contexts to the "next version", I can update them
all at the same time easily?
Any suggests are much appreciated. Thanks!
-Sean W
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
