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

Sven Meier updated WICKET-3962:
-------------------------------

    Attachment: select-option-uuid.patch

IMHO we should align Select/SelectOption with how CheckGroup/Check works, i.e. 
using a uuid as value.
This would fix this bug too.

See attached patch.

> the wrong option in select components is rendered (Combination of reusing 
> panels and defaultFormProcessing==false)
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3962
>                 URL: https://issues.apache.org/jira/browse/WICKET-3962
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.4.18, 1.5-RC5.1
>         Environment: mac os / windows / java 1.5 / java 1.6 / tomcat
>            Reporter: Olaf Siefart
>              Labels: defaultFormProcessing, select
>         Attachments: select-option-uuid.patch, wicket-3962.zip
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> We are reusing a panel (let's say a PersonPanel, two instances). There is a 
> forward / back ajax-navigation between the panels, which is implemented with 
> component.replace. So the component path for the select of both panels are 
> the same. The back-function is implemented with 
> setDefaultFormProcessing(false). If now showing PersonPanel1 --> Forward --> 
> PersonPanel2 --> Back --> PersonPanel1 --> Forward --> PersonPanel2, the 
> selects of the panel 2 are showing the values of panel1.
> The Reason:
> In the 'Select.isSelected(...)'  the getInputAsArray() is used (instead of 
> the getRawInput()). So request parameters are overruling the raw input, if 
> the component path is the same.
> Wicket-Code:
> if (hasRawInput()) {
>   String[] paths = getInputAsArray();
> I think, instead of calling getInputAsArray() the getRawInput()(With a split 
> for the MultiSelect-support) should be used.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to