Prev: trustAnchors parameter must be non-empty
Next: Splash screen
From: rpnz on 6 Apr 2010 19:27
On Apr 1, 10:54 am, Lew <no...(a)lewscanon.com> wrote:
> znôrt wrote:
> > On Tue, 30 Mar 2010 23:08:23 +0300, rpnz <raj...(a)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

Thought I found a solution using webdefault.xml as the
defaultsDescriptor, and then creating some context parameters.
Only problem is that images are not showing up on the web app. The
request log states a 404 when requesting the image. ie

127.0.0.1 - - [07/Apr/2010:11:16:22 +1200] "GET /ais/gfx/menubtn/
MenuBtn_advanced.png HTTP/1.1" 404 0

Any ideas ?
First  |  Prev  | 
Pages: 1 2
Prev: trustAnchors parameter must be non-empty
Next: Splash screen