In fact I think I am confronted with two different issues :
1 - @Persist behavior
When I use a @Persist, I am aware that the object will only be kept in
'memory' between two request on the same page / component. So in my head I
thought that it was always the same object (the same instance of the object)
used by the BeanEditForm all along the process :
Display Page A -> Submit Form in page A -> Display Page A again
<----- Same instance of my User object because of the @Persist -----> ==>
Wrong ! (at least inside the BeanEditForm)
2 - Mecanism of the BeanEditForm : It recreate an entire object when I
submit the form. That is why it work with the ASO. Because it is always the
same instance of the object that is updated. In fact when using the @Persist
it does not have any effects on the BeanEditForm.
So... would not it be possible to make the @Persist work the same way that
ASO in this particular case ? It would be very usefull. Hibernate object
manipulation/update would be very easy and powerfull.
Ex :
1 - Get my User from Hibernate
2 - Pass it to the BeanEditForm
3 - Update the date directly in the bean (because the @Persist would allow
to do so )
4 - use onSuccess to do a Merge and a Commit :)
What is your opinion about that ?
Regards,
Martin
--
View this message in context:
http://www.nabble.com/-T5--Instantiate-%22Interfaces%22-tp18153603p18158657.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
