Re: [REVIEW] WebConfiguration - consolidation of web.xml configuration information

From: Ryan Lubke <Ryan.Lubke_at_Sun.COM>
Date: Wed, 05 Apr 2006 09:06:16 -0700

Ed Burns wrote:
>>>>>> On Tue, 04 Apr 2006 10:56:21 -0700, Ryan Lubke <Ryan.Lubke_at_Sun.COM> said:
> RL> The aim of the change bundle is to provide:
> RL> - a central location for all web.xml configuration information
> RL> - bring a consistent naming scheme (camel hump) for RI
> RL> web configuration parameters
> RL> * introduce a deprecation facility to continue to
> RL> support any deprecated parameters with a log message
> RL> stating such
> RL> - inital work to allow the modification of these parameters
> RL> at runtime
> I could be missing something here, but I don't see a differentiation in
> the WebConfiguration between values that come into the system via
> <context-param> elements and those that come into the system via
> <init-param> elements. This code in WebConfiguration is an example:
> public String getInitParameter(WebContextInitParameter param) {
> return contextParameters.get(param);
> }
> These two elements have different meanings. Shouldn't that be reflected
> in the WebConfiguration API?
> Ed
AFAIK, servlet <init-params> are only available to the Servlet under
which they are specified,
so we wouldn't have access to their values. I can certainly change the
name of getInitParameter()
to getContextInitParameter() to remove any potential confusion.