Neither solution is good. I don't think running a full JVM for two versions of
an app makes sense for this application (it's way overkill), and more of a
hastle to maintain from an operations perspective. Using web.xml means modifying
the ear file for each app, I don't want to do this. I treat the web.xml file
like source code: it shouldn't change for minor variations. I need an external
config for the app that can be deployed separately from the ear file. It would
be trivial if orion was like, say, resin, and let you set extra parameters in
the server.xml file. Or even if the orion-xyz.xml files worked as expected.
Tony Wilson <[EMAIL PROTECTED]> on 01/09/2001 18:37:47
Please respond to Orion-Interest <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
cc: (bcc: Ari Halberstadt/Lycos)
Subject: RE: how to set environment properties for an app?
Have only one application per java instance. Each with their own
application.xml, and whatever other things they need.
Another option is to put the configuration items into the web.xml of each of
your apps, perhaps as initialization parameters to a startup servlet. That
startup servlet can then put those parameters into a configuration object
that is specific to your application.
Tony
