Re: [Springframework-rcp-dev] To bean or not to bean.

[Rogan D. <ro...@da...>]

Jan Hoskens wrote:
> Hi all,
> 

> The second issue is the main thing I've been pondering of: to bean or
> not to bean. Should we create the formModel based on beans (current
> situation) or based on class/interface? We could create a FormModel
> based on a class/interface, then set a FormObject when needed and
> provide a null handling. The method getFormObject might actually return
> null while no default constructor is needed. No bean at creation time is
> needed. Now for al this magic to happen, I need to inform you that the
> current implementation does rely on the beans plumbing of spring. This
> isn't bad, but does mean a that some serious refactoring/implementing is
> needed before this will work. Before I jump into this pit, I'm wondering
> if this all makes sense. Is this worth the trip? Would you benefit from
> this change? I'm guessing it would, but I'd like to have some feedback
> on this first.
> 
> ps: it might be that these things have been surfaced a while ago and
> that I'm just reopening the discussion. Haven't yet searched the mail
> archive. (I remember whining about this a year or so ago, but did I mail
> it??)
> 
> Kind Regards,
> Jan

Hi Jan,

Not having worked very heavily with FormModels, but struggling when I 
did, I agree with your analysis.

It DOES make more sense to have the FormModel based on a Class or 
Interface, rather than an instance.

Rogan