You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/13 17:11:17 UTC

[jira] [Closed] (TAP5-829) Provide metadata for beanviewers

     [ https://issues.apache.org/jira/browse/TAP5-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-829.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Provide metadata for beanviewers
> --------------------------------
>
>                 Key: TAP5-829
>                 URL: https://issues.apache.org/jira/browse/TAP5-829
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Erik Putrycz
>              Labels: bulk-close-candidate
>
> I tried to improve beanviewers by using annotations in the class displayed but unfortunately this is not possible currently.
> For editing, BeanEditContext is available, while for viewing only PropertyOutputContext provides metadata about the object being edited. A BeanDisplayContext would be a great addition for accessing the class being edited and retrieve annotations for instance.



--
This message was sent by Atlassian JIRA
(v6.2#6252)