Hi all,
I'm a newcomer, so let me start with the disclaimer: I first glanced at wicket on last Friday.. I've read back mostly the user list archive and also read some docs, but still I have an open question which I'd like to get an answer for.
I don't really understand the logic of Page instantiation in wicket apps. I added some log to the WicketExamplePage constructor and watched when it runs when browsing through the examples. Appearently, it instantiates the page class for each request in the Navomatic example, as it does for the GuestBook example, until its form gets posted for the first time. After then, it never does it.. anyone can please give a hint about the logic being used here? (I'm really worried about Page instantiations from performance point of view).
If you allow me an other comment, I truely miss a slightly more complicated example from the distribution. While I was wondering about using ListViews in the pages, I could not found an example which does not use an in-memory representation of the model (maybe it's my fault). There was one example which used some tricking about invalidating the model on each edit action, but I still feel that model-to-view binding a bit static. I'd love to see an example where the model is coming from the middleware and is dynamically binded to the wicket component, not where the components store the model either themselves or in the session.
I used the 0.9.19 release of both wicket and the examples (just fetching HEAD from cvs now).
thanks much in advance,
Kristof Jozsa
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
