tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "manuel aldana (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-679) Allow defining read-only fields inside bean-edit-form component
Date Fri, 01 May 2009 09:58:30 GMT
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

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.
You can reply to this email to add a comment to the issue online.

View raw message