Re: Jetty 5.1 Multiple Contexts with 1 war
zn??rt wrote:
On Tue, 30 Mar 2010 23:08:23 +0300, rpnz <rajpnz@gmail.com> wrote:
But alternatively we could copy the war and rename it.
Our biggest concern is to how each war will read a unique ini file for
that school.
I faced the same issue years ago (jboss 3 with tomcat) and solved it
that way. May be not so elegant, but I found it straightforward and
preferable to having to mess around with sepcific appserver deployment
specs (always a somewhat obscure topic). Just duplicate/rename not just
the war, but also the application name, unique (i.e., not shareable)
services, data sources if need be, etc. You can easily add this step to
your release build script which wil produce, say, 5 wars instead of one
(plus one with shareable stuff, maybe) from one single source, and
forget about it. Of course, you will have to adapt whatever clients to
have them look for the appropiate context or service, but it's my guess
that you would want to do that anyway.
Thinking outside the box, you could put an Apache Web Server (httpd) front end
on that puppy, and use its reverse-proxy capabilities to serve up different
apps under the ostensibly same context name.
I forget the details, but we did something like this at a project I was on a
few years ago. The different clients were "Developer", "Tester" and
"Customer" (or equivalent), each with its own version of the application, but
the reverse proxy gave all three a consistent way to access their individual
versions.
--
Lew