----- Original Message -----
From: "Igor Vaynberg" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, July 22, 2005 5:00 PM
Subject: RE: [Wicket-user] Newbie confused about PageableListView
I really prefer Tapestry's approach for
providing easy data accessing interfaces for components, it lets the user
know exactly what methods need to be provided and it gives a better view
of
how the component works.
I'm also Tapestry user, and just started evaluating Wicket yesterday.
Well, especially in the absence of User Guide to give me some overview of
Wicket basics, I am also confused about whole Component->IModel aproach in
Wicket. I understand MVC in general, and similarity with Swing, but I was
expecting that each component has it's own specific model interface. For
example, ListView accepts IModel interface in constructor, so I was digging
through Javadoc to find this LoadableDetachableModel where I would fetch
entities from my DAO bean.
And although I was suspecting it shoull return List of entities, I didn't
know until I tried. If there was something explicit like:
public interface ListViewModel {
public Iterator getItems();
}
and constructor like:
public ListView(String id, ListViewModel model)
there would be no doubt how to use this component.
And I'm still wondering how page navigation works :-( I read in javadocs
that when page gets instantiated, it is stored in user's session. But what
happens when same page gets instantiated mutliple times? It happens when one
goes to specific page with PageLink component for eg.
-Vjeran
-------------------------------------------------------
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
