notice this will break any existing user imodel subclasses. mostly it should
be trivial to fix, but if you do use the component argument in the get/set
object it will not be so trivial.
-igor
On 3/7/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
In 2.0 we have a model change:
IModel.getObject(Component) -> IModel.getObject()
IModel.setObject(Component,Object) -> IModel.setObject(Object)
So if you want to object from a component in 2.0 you only have to do:
component.getModel().getObject()
instead of
component.getModel().getObject(XXXX)
That XXX is depending on what kind of model you use. If the component
did inherit a CompoundModel then you have to specify the component.this
If you where owner of the compoundmodel then you shouldn't specify
anything (null)
This is all fixed in 2.0 and now we can backport it to 1.3:
1> port it to 1.3
2> don't port it to 1.3
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
