myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <>
Subject [jira] Commented: (MYFACES-793) Document outstanding issue with dataTable, commandSortHeader and input components
Date Tue, 08 Nov 2005 01:42:20 GMT
    [ ] 

Simon Kitching commented on MYFACES-793:

Sorry, minor issue in the patch: the description must be XML, not javadoc or HTML.

Here's my proposed new description for the commandSortHeader tag in tomahawk.tld; the whole
text is probably easier to deal with than a patchfile anyway.
Note that the <p></p> appears to be ignored anyway; the generated HTML page just
runs this all together as one paragraph.

            Clickable sort column header.
            Must be nested inside an extended data_table tag.
            This tag is derived from the standard command_link tag and
            has the additional attributes columnName and arrow.
            Note: In contrast to normal command links, the default for the "immediate"
            attribute is "true". This is desirable as it avoids validating all input
            fields in the enclosing form when the column sort order changes. HOWEVER
            when the <i>table</i> contains input components "immediate" <i>must</i>
            set to false; otherwise input fields will render blank after a sort, or
            will show their old values (ie will not appear to sort though output
            fields in the table will sort) when sort ordering is changed.

> Document outstanding issue with dataTable, commandSortHeader and input components
> ---------------------------------------------------------------------------------
>          Key: MYFACES-793
>          URL:
>      Project: MyFaces
>         Type: Improvement
>     Reporter: Simon Kitching
>  Attachments: tomahawk.tld-sortheader.patch
> Issue MYFACES-228 describes a problem with table sorting when the table has input components.
> That issue has been marked as closed even though the original problem was never resolved.

> There is a partial workaround: set immediate=false on the commandSortHeader. Attached
is a patch
> to at least document that this is necessary for commandSortHeader.
> Ideally the original bug would also be reopened, or this entry used as a continuation
of that issue, as the problem isn't properly resolved.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message