You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "James Carman (JIRA)" <ji...@apache.org> on 2008/06/13 00:54:45 UTC

[jira] Commented: (WICKET-767) Generify IModel

    [ https://issues.apache.org/jira/browse/WICKET-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604676#action_12604676 ] 

James Carman commented on WICKET-767:
-------------------------------------

Isn't this already done?  I'm pretty sure the consensus is that we at least need to generify IModel and it's already done.  So, are we good to resolve/close this?

> Generify IModel
> ---------------
>
>                 Key: WICKET-767
>                 URL: https://issues.apache.org/jira/browse/WICKET-767
>             Project: Wicket
>          Issue Type: Wish
>            Reporter: Willis Boyce
>             Fix For: 1.4-M3
>
>
> 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.