2007/4/25, Pierre van Rooden <[EMAIL PROTECTED]>:
Michiel Meeuwissen wrote:
> That will have the effect that you can set any module property in
> web.xml or in context tag (e.g. server.xml or the specific
> context.xml) of tomcat..
This already exists (in 1.9).
Parameters are read from the appli
2007/4/25, Pierre van Rooden <[EMAIL PROTECTED]>:
Michiel Meeuwissen wrote:
> That will have the effect that you can set any module property in
> web.xml or in context tag (e.g. server.xml or the specific
> context.xml) of tomcat..
This already exists (in 1.9).
Parameters are read from the appli
Michiel Meeuwissen wrote:
That will have the effect that you can set any module property in
web.xml or in context tag (e.g. server.xml or the specific
context.xml) of tomcat..
This already exists (in 1.9).
Parameters are read from the applicationcontext (overriding xml
configuration) during st
I'd like to add some code like:
if (value == null && MMBaseContext.isInitialized()) {
value
=MMBaseContext.getServletContext().getInitParameter(getName() + "." +
key);
}
to that method.
That will have the effect that you can set any module property in
web.xml or in context tag (e
I'd like to add some code like:
if (value == null && MMBaseContext.isInitialized()) {
value
=MMBaseContext.getServletContext().getInitParameter(getName() + "." +
key);
}
to that method.
That will have the effect that you can set any module property in
web.xml or in context tag (e
