Hello,
On 11/7/05, Steven McNeel [EMAIL PROTECTED] wrote:
I consider this sort of thing as analogous to MVC Front Controller (aka
Dispatcher) logic. I'm basically unclear as to where that logic belongs in
a Wicket app.
The fact is, while I'm still new in the area of Components based web
There sure is a mismatch; component based frameworks emerged because
of the mismatch Model 2 frameworks with page parts. Requests in Model
2 frameworks map to page wide actions. The controller/ view handler
has to ensure the state of all elements of the page are kept in sync
and rendered
Hello,I think I've read all of the pertinent articles in the documentation, especially http://www.wicket-wiki.org.uk/wiki/index.php/Lifecycle. On each request to my app, I first need to run a database query,the parameters of which are dependent on the parameters in the Request. Then I need to
On 11/7/05, Steven McNeel [EMAIL PROTECTED] wrote:
Hello,
I think I've read all of the pertinent articles in the documentation,
especially
http://www.wicket-wiki.org.uk/wiki/index.php/Lifecycle. On
each request to my app, I first need to run a database query,the parameters
of which are
And you are sure the queries you want to run are page/ component
independent, right? What you are doing is request based, which is
fine, but which is not nescesarily a component based way of doing
things.
Eelco
On 11/7/05, Steven McNeel [EMAIL PROTECTED] wrote:
Hello,
I think I've read all
It confused me just until 10 minutes ago. I agree with you that it should
be renamed if it is not already a too late.
Christian
I also think it is confusing if not misleading.
On Mon, 7 Nov 2005 23:53:16 +0100, Johan Compagner [EMAIL PROTECTED]
wrote:
ahh yes i see it
Got confused with
