click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Finn Bock (JIRA)" <>
Subject [jira] Commented: (CLK-558) Binding multi request parameter to Page class field
Date Thu, 01 Jul 2010 12:31:51 GMT


Finn Bock commented on CLK-558:

I don't see a problem with mixed types in the array. If the destination page defines it as
"public String[] option", then all is fine. If it defines it as double[] then we should get
an exception and an error page like we do already for normal "public double option":

ognl.OgnlException: id [java.lang.NumberFormatException: For input string: "$3"]
	at ognl.ObjectPropertyAccessor.setPossibleProperty(

But that's just IMO. What do others think?

> Binding multi request parameter to Page class field
> ---------------------------------------------------
>                 Key: CLK-558
>                 URL:
>             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.

View raw message