Craig R. McClanahan wrote:
Since we went to all the effort to change ApplicationConfig to
ModuleConfig in the first place, we should complete the task and banish it
from any non-deprecated APIs that we have. This whole change did make me
pretty squeamish :-), but a half-completed change is
On Mon, 25 Nov 2002, Ted Husted wrote:
> Date: Mon, 25 Nov 2002 16:49:31 -0500
> From: Ted Husted <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: PlugIn, Application
For the record, I'm with David. A beta is a beta. Any application
advanced enough to be using ApplicationConfig directly is advanced
enough to do a little renaming when moving from b2 to b3.
I support the commitment to provide backward compatability between
releases; but, IMHO, backward compat
avid
From: "Cumps, Jan {TROP}" <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: PlugIn, ApplicationConfig and Deprecated
Date: Mon, 25 Nov 2002 09:02:58 +0100
I have a problem w
I have a problem with the deprecated ApplicationConfig class, and still
requiring it in the PlugIn interface.
It is not possible to create a PlugIn implementation without refering to
ApplicationConfig (even when using PlugInPatch, you have to implement
PlugIn). This gives deprecate warnings.
Some
