The discussion is purely about IWrapModel and the getNestedModel() method of IModel.
What to do with both.
I think getting rid of IWrapModel will be a bit hard. Because we need to know on some places
that it is a wrapmodel.. so that we know we have to check for its nested one.
(look for example at Component.setModel())
And i know that getNestedModel() method of IModel is used ofter in a project
for getting the real internal model. But i think i am +1 to just move the getNestedModel()
to the IWrapModel and keep the IWrapModel.
johan
On 8/21/06, Eelco Hillenius <[EMAIL PROTECTED]
> wrote:
Hi guys,
How are we doing on models for 2.0? Is it getting stable? Can I start
writing about them? Or are there a couple of things on the todo list
still?
Eelco
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
