Struts might be more transparent in that it delivers you a flat model.
There's just that request and that one form comming in, and the form
is populated by matching incomming request parameters with formbean
properties. Furthermore, that formbean IS your model (and your only
one), instead of a faca
mmhh It did struck me for a while to understand the underlying concept of Wicket's model and the relationship with various components. One thing I notice, It seems that Struts deal with form backing model more transparent than Wicket does in terms of accessing the model object (or may be I'm just b
ncent Jenks
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, March 15, 2006 11:49 AM
Subject: Re: [Wicket-user] Newbie question: applying dynamic form component
with ListView
So, in a nutshell, my code could be refactored to eliminate the need for
Label objects in each row and in their place
So, in a nutshell, my code could be refactored to eliminate the need for Label objects in each row and in their place, use the model objects?On 3/15/06, Jonathan Cone
<[EMAIL PROTECTED]> wrote:
Hi Michael,
One thing that I personally think is important
to understanding ListView is knowi
Hi Michael,
One thing that I personally think is important
to understanding ListView is knowing that each item in the ListView is one
concrete model object instance. If you think about it, then you will see
you shouldn't need many(if any) collections in your form backing model
classes.
