Jeremy, I bought and read that book already. I have a good understanding of the 
technology now, but still feel lack of precise understanding of them. 

Cheers!


--- On Wed, 8/5/09, Jeremy Thomerson <[email protected]> wrote:

> From: Jeremy Thomerson <[email protected]>
> Subject: Re: How Wicket's big concepts/objects work together and in what  
> order?
> To: [email protected]
> Date: Wednesday, August 5, 2009, 4:51 PM
> Welcome to Wicket!  The best
> thing you can do is buy Wicket in Action.
>  It has charts that show the interactions between these
> various
> components.
> 
> --
> Jeremy Thomerson
> http://www.wickettraining.com
> 
> 
> 
> 
> On Wed, Aug 5, 2009 at 3:41 PM, David Chang<[email protected]>
> wrote:
> >
> > Hello, I am learning Wicket now and feel a bit
> confused by the new concepts in Wicket regarding how they
> work together and in what order.
> >
> > The big concepts I am talking about include:
> >
> > Application
> > Session
> > Request
> > RequestCycle
> > RequestCycleProcessor
> > RequestTarget
> > SessionStore
> > Request
> > Response
> >
> > Suppose I have a simple page with just one Wicket
> label. A user requests this page. I would like to know how
> the above objects/concepts get involved and in what order.
> >
> > If it needs too much description, then forget it. If
> it does not take too much of your time or you want to
> refresh yourself by give me an explanation, I really
> appreciate it.
> >
> > I want to be a good Wicket programmer.
> >
> > Thank you!
> >
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to