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

[Darren D. <dda...@kg...>]

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

+1 : setCommandName is much clearer.

> The same applies to our various notions of XML bean references. I'd 
> like to drop support for the deprecated <ref external=".../> as of 
> 1.0 RC1, and suggest to proceed similarly with 
> BaseCommandController's setBeanName. If we communicate that clearly, 
> 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