Tapestry should support keeping a page field in serialized form instead of
holding a reference to
-------------------------------------------------------------------------------------------------
Key: TAPESTRY-1977
URL: https://issues.apache.org/jira/browse/TAPESTRY-1977
Project: Tapestry
Issue Type: New Feature
Components: Framework
Affects Versions: 5.0.6
Reporter: Hugo Palma
Priority: Minor
This would be really useful in CRUD application where you want to edit an
object instance that is a persistent page property. The problem with the
current solution is that Tapestry always holds the reference to the object, so
when Tapestry resets to the default value it's actually assigning the reference
of the changed object. This means that the actually resetting has to be done by
the application code.
Maybe this could be a new parameter of the Persist annotation indicating if you
want to persist as a reference or in a serialized form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]