Re: How Wicket's big concepts/objects work together and in what order?
This idea of 'just doing it' and a culture of incremental knowledge attainment is crucial in my book. I've made a point of building the most trivial webapps I have in wicket. For example we recently re-did our WISP public homepage ( http://www.valleyinternet.com/) and I used it as an opportunity to learn more wicket. The page is simple and minor andbarely worthy of 'wicketizing' but doing something that specifically does -not- have a huge audience and does -not- have massive features is a great way to learn more without the pressures of developing a "real" app. In that case I got to work with GMap2, learned some new ajax interactions (including some gotchas) and was able to decisively break from my Ant past and fully embrace Maven. So we got a new homepage but I got to pick up new techniques that I am now applying to other trivial (and not so trivial) webapps. So, DO IT but do it often.. John- On Thu, Aug 6, 2009 at 5:29 AM, T Ames wrote: > I think for most people anyway, you learn by doing. I would think that by > now you have a basic understanding to put together a really decent web > application. There is quite a learning curve, but you do not have to > understand all of the internals. > > I learn more about Wicket each time I do a web app. I don't think you > could > really be a "good" Wicket programmer unless you have several apps under > your > belt. Just go in a DO IT! The understanding will come with experience. > > > > On Thu, Aug 6, 2009 at 7:54 AM, jWeekend >wrote: > > > > > David, > > > > Jonathan Locke and I have started writing an article describing the > Wicket > > architecture (as opposed to the Architecture of A Wicket Application). It > > will be the document I wish could have found when I had the good fortune > to > > come across Wicket in 2007. > > > > In the meantime, we have a few articles on the wiki by Dima (pen name > syl) > > like > > > > > http://cwiki.apache.org/WICKET/request-cycle-and-request-cycle-processor.html > > this that you may find useful. > > > > Regards - Cemal > > jWeekend > > OO, Java Technologies, Wicket - Training & Consultancy > > http://jWeekend.com > > > > > > > > David Chang-5 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: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > > > > -- > > View this message in context: > > > http://www.nabble.com/August-London-Wicket-Event-%28just-a-drink-%29-tp24834574p24845115.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
Re: How Wicket's big concepts/objects work together and in what order?
I think for most people anyway, you learn by doing. I would think that by now you have a basic understanding to put together a really decent web application. There is quite a learning curve, but you do not have to understand all of the internals. I learn more about Wicket each time I do a web app. I don't think you could really be a "good" Wicket programmer unless you have several apps under your belt. Just go in a DO IT! The understanding will come with experience. On Thu, Aug 6, 2009 at 7:54 AM, jWeekend wrote: > > David, > > Jonathan Locke and I have started writing an article describing the Wicket > architecture (as opposed to the Architecture of A Wicket Application). It > will be the document I wish could have found when I had the good fortune to > come across Wicket in 2007. > > In the meantime, we have a few articles on the wiki by Dima (pen name syl) > like > > http://cwiki.apache.org/WICKET/request-cycle-and-request-cycle-processor.html > this that you may find useful. > > Regards - Cemal > jWeekend > OO, Java Technologies, Wicket - Training & Consultancy > http://jWeekend.com > > > > David Chang-5 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: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > -- > View this message in context: > http://www.nabble.com/August-London-Wicket-Event-%28just-a-drink-%29-tp24834574p24845115.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: How Wicket's big concepts/objects work together and in what order?
David, Jonathan Locke and I have started writing an article describing the Wicket architecture (as opposed to the Architecture of A Wicket Application). It will be the document I wish could have found when I had the good fortune to come across Wicket in 2007. In the meantime, we have a few articles on the wiki by Dima (pen name syl) like http://cwiki.apache.org/WICKET/request-cycle-and-request-cycle-processor.html this that you may find useful. Regards - Cemal jWeekend OO, Java Technologies, Wicket - Training & Consultancy http://jWeekend.com David Chang-5 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: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View this message in context: http://www.nabble.com/August-London-Wicket-Event-%28just-a-drink-%29-tp24834574p24845115.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How Wicket's big concepts/objects work together and in what order?
will do. thanks! --- On Wed, 8/5/09, Igor Vaynberg wrote: > From: Igor Vaynberg > Subject: Re: How Wicket's big concepts/objects work together and in what > order? > To: users@wicket.apache.org > 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 > 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 > 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 > wrote: > >> > >>> From: Igor Vaynberg > >>> Subject: Re: How Wicket's big concepts/objects > work together and in what order? > >>> To: users@wicket.apache.org > >>> 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 > >>> 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 > > >>> wrote: > >>> > > >>> >> From: Jeremy Thomerson > >>> >> Subject: Re: How Wicket's big > concepts/objects > >>> work together and in what order? > >>> >> To: users@wicket.apache.org > >>> >> 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 > >>> >> 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 > >>>
Re: How Wicket's big concepts/objects work together and in what order?
Jeremy, thanks for the good tip. It makes sense, though not the best way. The more I read about Wicket, the more I like it:-) Just hope to know every detail. Wicket is a great tool but learning curve is tall. --- On Wed, 8/5/09, Jeremy Thomerson wrote: > From: Jeremy Thomerson > Subject: Re: How Wicket's big concepts/objects work together and in what > order? > To: users@wicket.apache.org > Date: Wednesday, August 5, 2009, 5:35 PM > 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 > 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 > wrote: > > > >> From: Igor Vaynberg > >> Subject: Re: How Wicket's big concepts/objects > work together and in what order? > >> To: users@wicket.apache.org > >> 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 > >> 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 > >> wrote: > >> > > >> >> From: Jeremy Thomerson > >> >> Subject: Re: How Wicket's big > concepts/objects > >> work together and in what order? > >> >> To: users@wicket.apache.org > >> >> 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 > >> >> 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. > >&
Re: How Wicket's big concepts/objects work together and in what order?
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 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 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 wrote: >> >>> From: Igor Vaynberg >>> Subject: Re: How Wicket's big concepts/objects work together and in what >>> order? >>> To: users@wicket.apache.org >>> 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 >>> 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 >>> wrote: >>> > >>> >> From: Jeremy Thomerson >>> >> Subject: Re: How Wicket's big concepts/objects >>> work together and in what order? >>> >> To: users@wicket.apache.org >>> >> 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 >>> >> 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: users-unsubscr...@wicket.apache.org >>> >> > For additional commands, e-mail: users-h...@wicket.apache.org >>> >> > >>> >> > >>> >> >>> >> >>> - >>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> >> For additional commands, e-mail: users-h...@wicket.apache.org >>> >> >>> >> >>> > >>> > >>> > >>> > >>> > >>> - >>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> > For additional commands, e-mail: users-h...@wicket.apache.org >>> > >>> > >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How Wicket's big concepts/objects work together and in what order?
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 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 wrote: > >> From: Igor Vaynberg >> Subject: Re: How Wicket's big concepts/objects work together and in what >> order? >> To: users@wicket.apache.org >> 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 >> 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 >> wrote: >> > >> >> From: Jeremy Thomerson >> >> Subject: Re: How Wicket's big concepts/objects >> work together and in what order? >> >> To: users@wicket.apache.org >> >> 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 >> >> 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: users-unsubscr...@wicket.apache.org >> >> > For additional commands, e-mail: users-h...@wicket.apache.org >> >> > >> >> > >> >> >> >> >> - >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> >> >> > >> > >> > >> > >> > >> - >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How Wicket's big concepts/objects work together and in what order?
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 wrote: > From: Igor Vaynberg > Subject: Re: How Wicket's big concepts/objects work together and in what > order? > To: users@wicket.apache.org > 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 > 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 > wrote: > > > >> From: Jeremy Thomerson > >> Subject: Re: How Wicket's big concepts/objects > work together and in what order? > >> To: users@wicket.apache.org > >> 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 > >> 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: users-unsubscr...@wicket.apache.org > >> > For additional commands, e-mail: users-h...@wicket.apache.org > >> > > >> > > >> > >> > - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How Wicket's big concepts/objects work together and in what order?
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 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 wrote: > >> From: Jeremy Thomerson >> Subject: Re: How Wicket's big concepts/objects work together and in what >> order? >> To: users@wicket.apache.org >> 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 >> 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: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How Wicket's big concepts/objects work together and in what order?
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 wrote: > From: Jeremy Thomerson > Subject: Re: How Wicket's big concepts/objects work together and in what > order? > To: users@wicket.apache.org > 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 > 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: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How Wicket's big concepts/objects work together and in what order?
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 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: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
How Wicket's big concepts/objects work together and in what order?
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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org