You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/03/19 00:34:24 UTC

[jira] Commented: (TAPESTRY-2278) BlankOption value in Select component should be configurable

    [ https://issues.apache.org/jira/browse/TAPESTRY-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580171#action_12580171 ] 

Howard M. Lewis Ship commented on TAPESTRY-2278:
------------------------------------------------

Isn't this juse blankoption="never" ?

> BlankOption value in Select component should be configurable
> ------------------------------------------------------------
>
>                 Key: TAPESTRY-2278
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2278
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.11
>            Reporter: Sven Homburg
>             Fix For: 5.0.12
>
>
> i often use the option value of a select component holding id's for database entities.
> the id's type are most numeric values, so my problem is: 
> i attached an ajax request that sends each change from the select component.
> the following method catch the event
>     @OnEvent(component = "inputProject", value = "change")
>     JSONValue projectIdChanged(long projectId)
>     {
>        .....
>         return mapper.toJSON(resultList);
>     }
> if the user select the blank option
> the component throws a NumberFormatException
> so it were cool, if i declare the empty option value by my self.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org