[
https://issues.apache.org/jira/browse/WICKET-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-3866.
-------------------------------------
Resolution: Invalid
The proper way to set the type in the constructor is:
new TextField<Integer>("integer", integerModel, Integer.class);
new TextField<Integer>("integer", integerModel) is not enough because Java
doesn't preserve this information at runtime (generics erasure).
> Typecasted TextField ignores given Type
> ---------------------------------------
>
> Key: WICKET-3866
> URL: https://issues.apache.org/jira/browse/WICKET-3866
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.17, 1.5-RC5.1
> Environment: Windows 7, JDK 1.6.0_26
> Reporter: Paul
> Attachments: quickstart.zip
>
>
> Hi,
> while reading a Integer from a typecasted TextField I realised Wicket ignores
> the given Type and asumes a String. Only way to get another Type is to call
> the Function setType(). But using a typed contructor the usage of setType()
> should be obsolete and the TextField should assume the given type.
> I attached a Quickstart. Simply have a look at the HomePage and comment out
> Line 29.
> Cheers
> Paul
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
