Re: Bean editor model for User already contains a property model for property 'account'

[neo anderson <ja...@yahoo.co.uk>]

You are right. I think this is the scenario issue. I should use other way
(e.g. intermediate bean) for gethering User information. 

Thanks for all your help. That helps me have better understanding on related
Tapestry mechanism. 

I appreacite it. : )


cordenier christophe wrote:
> 
> If your purpose is to secure your bean property, i think you should create
> an intermediate bean for your User creation.
> Tapestry Form properties are mapped to bean properties, and properties are
> set simply via accessors.
> Tapestry requires an empty constructor to your bean, and this is how
> Tapestry instantiate an object for the form.
> 
> I might be wrong, but i think that if you do not want to modify your user
> 'model' (and add an setter) then you should use a specific bean for form
> interaction and create the complete User Entity (using constructor) in the
> success phase.
> 
> 

-- 
View this message in context: http://www.nabble.com/Bean-editor-model-for-User-already-contains-a-property-model-for-property-%27account%27-tp25531292p25712083.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org