[
https://issues.apache.org/jira/browse/TAP5-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-570.
-------------------------------
Resolution: Incomplete
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the
latest 5.4 preview release), feel free to provide the necessary information and
reopen.
> tapestry-core should provide a built-in page to show the status of persistent
> data
> -----------------------------------------------------------------------------------
>
> Key: TAP5-570
> URL: https://issues.apache.org/jira/browse/TAP5-570
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Igor Drobiazko
> Assignee: Igor Drobiazko
> Labels: bulk-close-candidate
> Attachments: TAP5-570-v2.patch, TAP5-570.patch
>
>
> In order to oprimize the amount of data persisted in the session via @Persist
> or as ASO one should be able to get an overview of it. A page StateStatus
> should be provided which could loo like:
> Persistant Fields
> ---------------------------------------------------------------------------------------------
> Strategy Name | Page Name | Component Id | Field Name
> ---------------------------------------------------------------------------------------------
> flash | Login | loginform.form |
> defaultTracker
> -----------------------------------------------------------------------------------------------
> state | Foo |
> | bar
> ------------------------------------------------------------------------------------------------
> Application State Objects
> ----------------------------------------------------------------------------------------------
> com.example.model.User@ba8180[id=1,username=root,.......]
> ----------------------------------------------------------------------------------------------
> com.example.model.Foo1f6c439[bar=baz]
> ----------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
