Hi,
Sorry, not sure I understand what you mean. A Label has a model and
the model value gets displayed. I guess the model value ist what you
call the Caption?
sorry, this example was wrong. Lets say you set the visibility of a
label to false, then it still is hidden in the next request (the
component and all the properties have a state). But this is not true
when the Label is in a list.
your model object can be any class, not just simple String. May I
suggest you read http://wicket.sourceforge.net/wiki/index.php/Models.
Yes, I'm aware of this. But from my point of view (maybe I'm wrong,
I'm not sure), I put view-only related information in the component
itself and not in it's model (for example like the visibility of
Wicket components). In my example, the information if the component
is collapsed or not is view related and managed by the component
itself at all and not by its model. At the moment my model objects
are beans which only contain the business data. I'm not sure if these
should get blown up (for example using a extended class) with view
state information...
I can use this approach even with lists when using
setOptimizeItemRemoval and cleaning up myself, but I'm wondering if
this is the right way...
Ralf
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
