Re: [Springframework-developer] webflow: improving FormAction

[Erwin V. <erw...@er...>]

I'm sure there are valid use-cases which are easily supported with a 
subclass like I showed, or with method injection as Keith mentioned. 
However, I don't think it is typically a good idea to have Spring manage 
'domain objects', and a form object is typically a domain object or a simple 
DTO. I would say the common case is that the Spring application context 
manages 'service objects': services, DAOs, controllers, ...

Erwin Vervaet
erw...@er...
----- Original Message ----- 
From: "Steven Devijver" <ste...@gm...>
To: <spr...@li...>
Sent: Thursday, April 07, 2005 5:09 PM
Subject: Re: [Springframework-developer] webflow: improving FormAction


> In case of a normalized domain model wizards will typically include
> form fields that span beyond the single class currently created by
> FormAction. Creating the form object in Spring offers the advantage
> that related entities could be set on the form object - as required.
> This would for example avoid that getPerson() would return null. It's
> just more flexible.
>
>>
>> Mmm, interesting idea, but I'm not sure we should add this (e.g. why 
>> doesn't
>> the
>> BaseCommandController has this feature?). Anyway, it would be trivial to 
>> do
>> this
>> in a FormAction subclass:
>>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>