Sounds like a bug. The constructors should actually call each other
instead of having a different setup. I'll fix that by redirecting the
protected AbstractFormModel(ValueModel, boolean)
to
protected AbstractFormModel(MutablePropertyAccessStrategy, boolean)
while creating its own BeanPropertyAccessStrategy. That should do the
trick.
Thanks for reporting.
Kind Regards,
Jan
On Tue, 2008-05-13 at 09:23 +0200, Julio Alberto Argüello Fernández
wrote:
> As it's posted in the forum
> (http://forum.springframework.org/showthread.php?p=179565), there
> seems to be a bug in AbstractFormModel.
>
> Below it's pasted my previous post:
>
> I have been treating a particular PropertyAccessStrategy in order to
> satisfy one user need. So, the construction of the form model has
> changed from:
> protected AbstractFormModel(ValueModel, boolean);
>
> to:
> protected AbstractFormModel(MutablePropertyAccessStrategy, boolean);
>
> After this, I have realized the form doesn't track dirty situations
> correctly. The second constructor doesn't invoke to
> prepareValueModel(formObjectHolder); and adding this call everything
> works fine again.
>
> Is there any reason to this omission?
>
> Thank you in advance
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ Springframework-rcp-dev mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm
|
