[jira] [Closed] (TAP5-679) Allow defining read-only fields inside bean-edit-form component

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade closed TAP5-679.
-------------------------------

    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.

> Allow defining read-only fields inside bean-edit-form component
> ---------------------------------------------------------------
>
>                 Key: TAP5-679
>                 URL: https://issues.apache.org/jira/browse/TAP5-679
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1
>            Reporter: manuel aldana
>              Labels: bulk-close-candidate
>
> inside bean-edit form it would be cool to have a component parameter where you define read-only fields. They should be closed for edition, still they should be visible (thus @NonVisual is not an option).
> I know it is hard to put all form requirements into one component (harder to understand, harder to document). But having read-only fields inside a form is a very common use case and in my view should be supported in the handy first class form component of tapestry.
> The syntax could look like:
> <beaneditform .... readonly="literal:foo,bar"/>
> or even better, to let it control through page class:
> <beaneditform .... readonly="prop:readOnlyParameters"/>
> for discussion see also http://www.nabble.com/-bean-edit-form--make-a-sub-set-of-parameters-visible-but-not-editable-td23111464.html



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