[
https://issues.apache.org/jira/browse/WICKET-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085275#comment-13085275
]
Sven Meier commented on WICKET-3962:
------------------------------------
I don't like the uuid too much either, but Check/CheckGroup and
Option/OptionGroup do it this way (for whatever reason). Note that these
components use getInputAsArray() too.
> 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: PageScopedValue.patch, Select.java,
> 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
