rc1 is out, why dont you try with that. -igor
On Sun, Nov 16, 2008 at 5:23 PM, Ilja <[EMAIL PROTECTED]> wrote: > P.S.By "my problem is solved" I mean, obviously, that I'll stick with m2 for > the time being. > Didn't mean to sound like that is ideal, or that I'm not concerned that the > problem appears in m3. > Let me know if I can do anything to help out with that. > Cheers, > ilja > > On Sun, Nov 16, 2008 at 5:15 PM, Ilja <[EMAIL PROTECTED]> wrote: > >> You guys will want to know this: >> I figured that perhaps the problem lies with Wicket1.4-m3. >> So I swapped it out for Wicket1.4-m2. >> I did not change my code at all. I didn't change anything else. All I did >> was swap out the two Wicket versions. >> >> After I switched to Wicket1.4-m2, the page worked fine. >> The page is now not being re-constructed at every request and keeps state >> as expected. >> >> So, my problem is solved, but do you guys still want me to send you more >> info? >> I could switch back to m3 and send to the URLs that are being generated >> (Igor and Jeremy asked for that). >> I could still try and add a link to the page under m3 and see if that would >> make a difference (Igor asked for that). >> >> Jeremy's question about accidentally constructing the page myself or >> redirecting to it from my onSubmit() method has, I believe, answered itself >> (no to both). >> >> jWeekend, I assume you're talking about a Maven Quick Start - I don't use >> Maven (I know, I know, I should) but if that's something that can be done >> quickly and for which you could give me a pointer or two, I can try to do >> it. If you're still interested, that is. >> >> Let me know. >> >> Thanks to each of you for the help, I appreciate it! >> >> ilja >> >> On Sun, Nov 16, 2008 at 12:49 PM, Jeremy Thomerson < >> [EMAIL PROTECTED]> wrote: >> >>> Put a breakpoint in your constructor (sounds like you already have) and >>> see what's calling it. Is it possible that you're constructing the page >>> yourself (accidentally for a page link or something)? >>> >>> Also - what's the URL after you submit the form? Are you redirecting to >>> the page in your onSubmit? >>> >>> >>> Jeremy Thomerson >>> http://www.wickettraining.com >>> -- sent from a wireless device >>> >>> >>> -----Original Message----- >>> From: Ilja <[EMAIL PROTECTED]> >>> Sent: Sunday, November 16, 2008 2:06 PM >>> To: users@wicket.apache.org >>> Subject: Re: Why is my page stateless, and how do I make it stateful? >>> (using Wicket 1.4-m3) >>> >>> Hi Igor, thanks for the response. >>> No, I don't mean when I press the refresh button. Here's exactly what >>> happens: >>> >>> - I type the URL into my browser. In my debugger, I can see that a new >>> page >>> is constructed (the page constructor runs). >>> - There is a form on the page. I type something into the form (something >>> that won't pass form validation). >>> - I click on the form submit button. In my debugger, I can see that a >>> whole >>> new page is constructed (losing, of course, any state I had in the >>> previous >>> page). >>> - Even though a new page is constructed, the form is returned to me with >>> the >>> values filled in and a validation error. >>> I know this sounds very strange. But it's true, I've tested it many times. >>> >>> The same thing happens when I fill in the form with values that will pass >>> validation: >>> - When I click the form submit button, I can see in my debugger that a >>> whole >>> new page is constructed, and THEN the onSubmit() method of my form is >>> executed. Somehow, values filled into the form are retained even though a >>> whole new page was constructed. Other state in the page is lost. >>> Again, I know it sounds very strange. >>> >>> I've tested some other pages in my application and they do not show this >>> behavior. >>> The only difference between this particular page and the other pages is >>> that >>> for each of the other pages, a user has to be logged into the application. >>> The page in question, on the other hand, is a publicly accessible page for >>> which you do not have to be logged in. However, I don't see how that would >>> result in the behavior I see. >>> Also, the page in question uses PageParameters to receive some initial >>> values. But, again, I don't see how that would result in what I see. >>> I've also tried to get some info by calling isStateless() on the page but >>> it >>> returns null. >>> >>> What else could I try/what other info could I collect? >>> >>> Thanks for the help! >>> >>> ilja >>> >>> On Sun, Nov 16, 2008 at 9:09 AM, Igor Vaynberg <[EMAIL PROTECTED] >>> >wrote: >>> >>> > a page with a form on it cannot be stateless. what do you mean >>> > reconstructing on every request? when you press the refresh button? >>> > that is because this is a bookmarkable url... >>> > >>> > -igor >>> > >>> > On Sun, Nov 16, 2008 at 12:54 AM, Ilja <[EMAIL PROTECTED]> >>> wrote: >>> > > Hi, >>> > > I have a mounted, bookmarkable page with a form in it. >>> > > >>> > > My problem is that I want to keep state in the page. However, at every >>> > > request, the page is constructed anew and, obviously, I lose the state >>> > I'd >>> > > like to keep. >>> > > >>> > > At the same time (and this mystifies me a little), form components >>> seem >>> > to >>> > > keep state between requests during validation (non-form components, >>> such >>> > as >>> > > Labels, which are also included in my form class, do not keep state). >>> > > >>> > > So, since the page is re-constructed at every request, am I dealing >>> with >>> > a >>> > > stateless page (even though the form seems to keep some state)? >>> > > And how could I make that page stateful? >>> > > (I've tried setting setStatelessHint(false) on the page but that >>> doesn't >>> > > make a difference). >>> > > Why is the page stateless even though it has a stateful component (the >>> > form) >>> > > in it? >>> > > >>> > > I've scoured the Wiki and can't seem to find an answer to this >>> problem. >>> > > >>> > > Any thoughts would be appreciated! >>> > > >>> > > Thanks! >>> > > >>> > > ilja >>> > > >>> > >>> > --------------------------------------------------------------------- >>> > 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]
