RE: [Springframework-developer] BaseCommandController: setBeanName -> setCommandName

[<jue...@we...>]

Darren,

RC1 is planned for early December, and should indeed represent a feature =
freeze. The goal is to release a proper 1.0 final in early January, =
allowing for one month of intense testing, and for polishing of =
documentation. If we don't encounter any obstacles, we will *not* =
release a further milestone M4 before RC1.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Darren Davison
Sent: Friday, November 21, 2003 12:30 PM
To: spr...@li...
Subject: Re: [Springframework-developer] BaseCommandController:
setBeanName -> setCommandName



> Of course, setBeanName is a *very* commonly called method in=20
> command/form controller initialization. I consider this a reason to=20
> change it before 1.0 final, as we would have to stick with it else.=20

+1 : setCommandName is much clearer.

> The same applies to our various notions of XML bean references. I'd=20
> like to drop support for the deprecated <ref external=3D".../> as of=20
> 1.0 RC1, and suggest to proceed similarly with=20
> BaseCommandController's setBeanName. If we communicate that clearly,=20
> we shouldn't cause any migration headaches.

What's the plan for RC1 - is it feature and API freeze once RC1 is =
released
with only bugs being considered afterwards?  Just wondering if anything
concrete was behind the changed naming strategy.


--
Darren Davison
Public Key: http://www.davison.uk.net/key.jsp


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer