Replacing @Persist("entity") with @PageActivationContext seems to do the
trick.
There was also talk of creatively coding the onActivate method starting with
version 5.3.
Of course, the onSuccess() is modified to
@CommitAfter
Object onSuccess()
{
session.saveOrUpdate(person); // rather than just persist
return personIndex;
}
Just curious what the best (new) practice is for this common design pattern
of Add/Update being driven by the same page/class etc.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Reuse-Edit-Create-tp5643323p5643333.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
