dev@javaserverfaces.java.net

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

From: Ed Burns <ed.burns_at_sun.com>
Date: Wed, 5 Apr 2006 06:46:16 -0700

>>>>> 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

-- 
| ed.burns_at_sun.com  | {home: 407 869 9587, office: 408 884 9519 OR x31640}
| homepage:         | http://purl.oclc.org/NET/edburns/
| aim: edburns0sunw | iim: ed.burns_at_sun.com
| 29 Business Days until JavaOne SF 2006