You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Felix Röthenbacher (JIRA)" <de...@myfaces.apache.org> on 2010/11/09 10:58:08 UTC

[jira] Created: (TRINIDAD-1957) tr:selectManyShuttle with required="true" requires a selected item in the leading and trailing list box to pass validation.

tr:selectManyShuttle with required="true" requires a selected item in the leading and trailing list box to pass validation.
---------------------------------------------------------------------------------------------------------------------------

                 Key: TRINIDAD-1957
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1957
             Project: MyFaces Trinidad
          Issue Type: Bug
          Components: Components
    Affects Versions: 1.2.13-core ,  1.2.15-core 
            Reporter: Felix Röthenbacher
         Attachments: SelectManyShuttleRenderer.diff.txt

The selectManyShuttle component with required="true" imposes a required validation rule on each of its list boxes. This requires that not only an item has to be selected (moved from leading to trailing) but also that each list box must have an active selection (highlighted item) to pass validation. While this holds true if the user moves an item from one list to the other, it doesn't if the component is populated already and the user doesn't change anything. In this case the validation fails with a Field Error alert for each list box saying that at least one item has to be selected.

The patch provided sets the required attribute for the child listboxes to false as this validation rule is already imposed by the parent component. The patch also updates the tests.

I haven't checked it but quite possibly also the 2.0.x trunk is affected by this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TRINIDAD-1957) tr:selectManyShuttle with required="true" requires a selected item in the leading and trailing list box to pass validation.

Posted by "Felix Röthenbacher (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/TRINIDAD-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Röthenbacher updated TRINIDAD-1957:
-----------------------------------------

    Status: Patch Available  (was: Open)

> tr:selectManyShuttle with required="true" requires a selected item in the leading and trailing list box to pass validation.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1957
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1957
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.2.13-core ,  1.2.15-core 
>            Reporter: Felix Röthenbacher
>         Attachments: SelectManyShuttleRenderer.diff.txt
>
>
> The selectManyShuttle component with required="true" imposes a required validation rule on each of its list boxes. This requires that not only an item has to be selected (moved from leading to trailing) but also that each list box must have an active selection (highlighted item) to pass validation. While this holds true if the user moves an item from one list to the other, it doesn't if the component is populated already and the user doesn't change anything. In this case the validation fails with a Field Error alert for each list box saying that at least one item has to be selected.
> The patch provided sets the required attribute for the child listboxes to false as this validation rule is already imposed by the parent component. The patch also updates the tests.
> I haven't checked it but quite possibly also the 2.0.x trunk is affected by this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TRINIDAD-1957) tr:selectManyShuttle with required="true" requires a selected item in the leading and trailing list box to pass validation.

Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/TRINIDAD-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf updated TRINIDAD-1957:
-----------------------------------------

       Resolution: Fixed
    Fix Version/s:  1.2.15-core 
         Assignee: Matthias Weßendorf
           Status: Resolved  (was: Patch Available)

Tx to Felix Röthenbacher for the patch!

> tr:selectManyShuttle with required="true" requires a selected item in the leading and trailing list box to pass validation.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1957
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1957
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.2.13-core ,  1.2.15-core 
>            Reporter: Felix Röthenbacher
>            Assignee: Matthias Weßendorf
>             Fix For:  1.2.15-core 
>
>         Attachments: SelectManyShuttleRenderer.diff.txt
>
>
> The selectManyShuttle component with required="true" imposes a required validation rule on each of its list boxes. This requires that not only an item has to be selected (moved from leading to trailing) but also that each list box must have an active selection (highlighted item) to pass validation. While this holds true if the user moves an item from one list to the other, it doesn't if the component is populated already and the user doesn't change anything. In this case the validation fails with a Field Error alert for each list box saying that at least one item has to be selected.
> The patch provided sets the required attribute for the child listboxes to false as this validation rule is already imposed by the parent component. The patch also updates the tests.
> I haven't checked it but quite possibly also the 2.0.x trunk is affected by this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.