I’ll like to take
you up on the discussion. I see the following pros
and cons with this approach: Pro setObject: Allows the user to
implement logic into the model If so desired
Con setObject:
I do think that that
using setObject on the model is something that always should be done; it
creates a lot of flexibility and why have setObject if not to use it, if not it
will only cause confusion. -regards Nino From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Igor Vaynberg components whose model is
backed by a collection do not always call setobject() because they work on the
collection directly so there is no need to call On 7/17/06, Nino
Wael <[EMAIL PROTECTED]>
wrote: Strange then, it seems as the extension palette does not update on a
submit? Does it somehow detach from its model? |
------------------------------------------------------------------------- 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