[
https://issues.apache.org/jira/browse/TAPESTRY-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2278.
------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
When generating your SelectModel, you should include your own blank option with
value "0" to get the behavior you desire. Alternately, change the parameter
type from long to String and do your own parse to long (along with a check).
But don't expect Tapestry to treat the empty string exactly like the number
zero, that is a bad idea.
> 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
> Assignee: Howard M. Lewis Ship
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
