[
https://issues.apache.org/jira/browse/WICKET-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513782
]
Eelco Hillenius commented on WICKET-767:
----------------------------------------
Yes, this is one of the major things we're planning to re-introduce (we had
this in the 2.0 branch) for Wicket 1.4. Unfortunately (imho) we can't generify
models without also generifying components as well. Personally, I'm not crazy
about the change, but from earlier threads we can conclude that most people are
in favor of it.
We'll start working on this once 1.3 is final.
> Generify IModel
> ---------------
>
> Key: WICKET-767
> URL: https://issues.apache.org/jira/browse/WICKET-767
> Project: Wicket
> Issue Type: Wish
> Affects Versions: 1.2.6
> Reporter: Willis Boyce
>
> I find myself writing custom IModel implementations that depend on the
> underlying object being some specific type. It would be nice if I could get
> some type safety using generics, e.g.
> class MyCustomModel implements IModel<MyCustomObject>
> {
> MyCustomObject getObject(Component component) { ... }
> ...
> }
> I imagine that this has already been suggested, but I couldn't find a JIRA
> issue about it in the road map.
> I don't think that the core Wicket code would change too much, except in
> cases where the code actually cared what was in the model. Elsewhere it can
> just use IModel<?>.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
