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

Ulrich Stärk updated TAP5-679:
------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated more than 1.5 years ago, has no assignee, 
affects an old version of Tapestry that is not actively developed anymore, and 
is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of 
Tapestry, please update it as soon as possible. In the case of a feature 
request, please discuss it with the Tapestry developer community on the 
d...@tapestry.apache.org mailing list first.
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to