Here is the new implementation :
- the class WebConfiguration has been split into smaller classes for
each type. Everything is in a web sub package.
- an AppletConfiguration has been introduced
- 100% test coverage this time :) But I had to tweak the mocks.
- I added a TestAbstractConfiguration cl
Good point I forgot this one. I wonder if I should keep everything in
the same class or split the class into a ServletConfiguration,
FilterConfiguration, AppletConfiguration, etc. The WebConfiguration
could break in a servlet 2.2 environnement due to the lack of servlet
filters, this may be an
-Original Message-
> From: Oliver Heger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 02, 2004 7:43 AM
> To: Jakarta Commons Developers List
> Subject: Re: [configuration] WebConfiguration
>
>
> I also often run in the problem of converting data types and writing
> that
I also often run in the problem of converting data types and writing
that Integer.parseInt() stuff. It would be very nice to have a tool that
implements exactly that. I have something in mind that can be wrapped
over a container object, which implements a generic interface (e.g. a
simple getObj
What about one that's more generic. The WebConfiguration object
is being used as a type translator for a simple value get.
The technique here would be reflect into and convert type
public void init(ServletConfig config) {
try {
MapUtil config = new MapUtil(config, "initParameter");
That has ssome good taste... I would add an "applet-parameter"-based
one as well...
paul
On 1-Mar-04, at 19:02 Uhr, Emmanuel Bourg wrote:
Hi, I'd like to suggest a new configuration implementation that
bridges between parameters commonly used in web applications (servlet,
filter, application
