Model is like a box. It is just a container. Put your object in and get it back out. PropertyModel lets you put an object in the box and always lookup a value on that object, and set that value CompoundPropertyModel merely removes the string setting which value is pointing to the object and uses the Wicket:id of the corresponding component to reference the property
The examples Steve linked in the wiki are great. -Clint On Thu, Nov 10, 2011 at 10:33 PM, raju.ch <raju.challagun...@gmail.com>wrote: > Could someone please explain me the difference between Model , > PropertyModel,CompoundPropertyModel? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/What-is-the-difference-between-Model-PropertyModel-CompoundPropertyModel-tp4030452p4030452.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
