will do. thanks! --- On Wed, 8/5/09, Igor Vaynberg <[email protected]> wrote:
> From: Igor Vaynberg <[email protected]> > Subject: Re: How Wicket's big concepts/objects work together and in what > order? > To: [email protected] > Date: Wednesday, August 5, 2009, 5:37 PM > and when you do figure it out dont > forget to take the time to update > that lacking wiki page. > > -igor > > On Wed, Aug 5, 2009 at 2:35 PM, Jeremy > Thomerson<[email protected]> > wrote: > > The best way for you to see how each of those things > gets involved is > > to create the basic page that you mentioned - with a > label. Then set > > a debug point in your editor in the WicketFilter's > doFilter method and > > step through. Or, go the opposite way - set a couple > debug points in > > Label (i.e. onComponentTag, onBeforeRender, > onComponentTagBody, etc) > > and then when it breaks there, walk up the stacktrace > and see what's > > calling what. > > > > -- > > Jeremy Thomerson > > http://www.wickettraining.com > > > > > > > > > > On Wed, Aug 5, 2009 at 4:29 PM, David Chang<[email protected]> > wrote: > >> > >> Igor, thanks for the tip. I read that wiki page > "The Life-Cycle of a Wicket Application". The page has > useful info but it is still lacking. It does not mention > RequestCycleProcessor, RequestTarget, or Response objects. > Can any Wicket expert update this page? > >> > >> > >> Have a better understanding now but hope to have > more explanation. > >> > >> > >> --- On Wed, 8/5/09, Igor Vaynberg <[email protected]> > wrote: > >> > >>> From: Igor Vaynberg <[email protected]> > >>> Subject: Re: How Wicket's big concepts/objects > work together and in what order? > >>> To: [email protected] > >>> Date: Wednesday, August 5, 2009, 5:05 PM > >>> step 1) go to http://www.google.com > >>> step 2) in text box type "wicket lifecycle" > without the > >>> quotes > >>> step 3) hit "i am feeling lucky button" > >>> > >>> -igor > >>> > >>> On Wed, Aug 5, 2009 at 1:56 PM, David > Chang<[email protected]> > >>> wrote: > >>> > > >>> > 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] > >>> > > >>> > > >>> > >>> > --------------------------------------------------------------------- > >>> 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] > > > > > > --------------------------------------------------------------------- > 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]
