[
https://issues.apache.org/jira/browse/CLK-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884201#action_12884201
]
Md. Jahid Shohel commented on CLK-558:
--------------------------------------
Hi Finn,
Then there will be many cases (at least all number primitives) that we have to
cover. But what will happen if the values are mixed types? I mean on the source
page-
<input type="checkbox" name="option" value="1.0"/>
<input type="checkbox" name="option" value="2"/>
<input type="checkbox" name="option" value="$3"/>
And on the destination page, should we expect a string[] Or double[]? Since its
$3, it will not work for double[]. And there are many other cases like that.
Considering these cases, do you think keeping them as string will be ok? Or we
should add all those checkings for all primitives? Until now we support string,
number(all 6 types of number) and boolean. Let me know, I will fix that then.
> Binding multi request parameter to Page class field
> ---------------------------------------------------
>
> Key: CLK-558
> URL: https://issues.apache.org/jira/browse/CLK-558
> Project: Click
> Issue Type: New Feature
> Components: core
> Reporter: Naoki Takezoe
> Attachments: CLK-558-test.patch, CLK-558.patch
>
>
> Click can bind request parameters to Page class public fields.
> However it can not bind multi parameter to an array or list field.
> I propose adding multi parameter binding support to
> ClickServlet#processPageRequestParams()
> For example, here is the HTML which send a multi parameter.
> <input type="checkbox" name="option" value="1"/>
> <input type="checkbox" name="option" value="2"/>
> ...
> Click would bind this parameter to array or list public field
> of the Page class such as...
> public String[] option;
> or
> public List<String> option;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
