We don't do anything like that. For us, servlet context params must
be set in web.xml.
I would be willing to consider allowing them to be overridden in the
geronimo plan for that web app, but I don't think it's a good idea to
have a global override across web apps. You could try convincing me
otherwise :-)
Another mechanism you might consider is using system properties. We
have a gbean that lets you set as many system properties as you want,
and of course they are available to all applications. There's an
example of this gbean in the rmi-naming plan/configuration.
thanks
david jencks
On Jan 24, 2006, at 4:37 AM, Edson Carlos Ericksson Richter wrote:
I'll sumarize my question:
there is somenthing like Tomcat's "<Parameter .../>" in Geronimo
that I can use to define web app parameters in a server globally way?
Richter
Edson Carlos Ericksson Richter escreveu:
Hi!
I have app that users context parameters to define app behaviour
for each deployment. So, if I put context parameters inside
web.xml I running in the risk to override configuration for some
server (what is not desirable).
Under Tomcat, I used to define this kind of parameter in
context.xml for each deployment, like this:
<Context>
...
<Parameter name="containeType" value="D" override="false"/>
<Parameter name="appletLoginLocal" value="false" override="false"/>
...
</Context>
So, even if I put something in web.xml for above parameters,
Tomcat will assume values defined in context.xml
There is something similar in Geronimo?
Thanks,
Richter
