You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2009/09/26 12:57:15 UTC

[jira] Resolved: (WICKET-2403) org.apache.wicket.markup.html.tree.WicketTreeModel should have a constructor taking a TreeModel

     [ https://issues.apache.org/jira/browse/WICKET-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-2403.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-M1
         Assignee: Juergen Donnerstag

added constructor

> org.apache.wicket.markup.html.tree.WicketTreeModel should have a constructor taking a TreeModel
> -----------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2403
>                 URL: https://issues.apache.org/jira/browse/WICKET-2403
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4-RC6
>            Reporter: Florent Legendre
>            Assignee: Juergen Donnerstag
>             Fix For: 1.5-M1
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> org.apache.wicket.markup.html.tree.WicketTreeModel has no constructor yet. It forces the user to do the job a constructor should typically take care of consisting of:
> <code>
> private static IModel getModelForTreeModel(final TreeModel treeModel){
>         final WicketTreeModel wicketTreeModel = new WicketTreeModel();
>         wicketTreeModel.setObject(treeModel);
>         return wicketTreeModel;
> }
> </code>
> Nice if such a constructor could make it in 1.4 final.

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