Hi there. I'm bringing to life this old thread to ask whether this issue was
solved and how, because I'm experiencing something alike, which makes
session messsages to get lost ("consummed" by the first instance of the
page), and consecuently not shown by the second page instance.Thanks, Esteban Vinayak Borkar wrote: > > Martijn, > > Ok. I set the getStatelessHint() to return false. > > Now I get java.lang.IllegalStateException: No SessionHandler or > SessionManager > > What is the reason that wicket needs to instantiate the page twice? I > can understand the second instantiation, but my guess is that the first > instantiation is not to render the HTML. > > If I am correct about my analysis above, is there some way I can know > that the instantiation does not need to populate all the components? > > Thanks, > > Vinayak > > Martijn Dashorst wrote: >> Your page is stateless, which is a holy grail for most to attend. Be >> happy :) >> >> Since it is stateless, Wicket has to construct the page with each >> request, until it is no longer stateless. >> >> If you have a form, override its getstatelesshint method and return >> false. >> >> Martijn >> >> On Tue, Mar 31, 2009 at 8:36 AM, Vinayak Borkar <vbo...@yahoo.com> wrote: >>> Jeremy, >>> >>> I did that. The first time it is >>> >>> at >>> org.apache.wicket.request.target.component.BookmarkableListenerInterfaceRequestTarget.processEvents(BookmarkableListenerInterfaceRequestTarget.java:127) >>> >>> and the second time it is >>> >>> at >>> org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.processEvents(BookmarkablePageRequestTarget.java:223) >>> >>> >>> Does that help? >>> >>> Thanks, >>> Vinayak >>> >>> >>> Jeremy Thomerson wrote: >>>> Run it in debug mode, put a breakpoint in your constructor and see >>>> what's >>>> instantiating each. A lot of times it is your own code (a bad link, >>>> etc). >>>> >>>> -- >>>> Jeremy Thomerson >>>> http://www.wickettraining.com >>>> >>>> >>>> >>>> On Tue, Mar 31, 2009 at 1:30 AM, Vinayak Borkar <vbo...@yahoo.com> >>>> wrote: >>>> >>>>> Hello, >>>>> >>>>> >>>>> I have a form that performs a search and shows a page with results. >>>>> The >>>>> result page also has the same form to do a repeat search. I noticed >>>>> that >>>>> the >>>>> SearchPage is instantiated twice when I do a search from the form on >>>>> the >>>>> result page. Is there a way to make sure that does not happen? The >>>>> search >>>>> page ends up doing the search twice. >>>>> >>>>> Thanks, >>>>> Vinayak >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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 > > > -- View this message in context: http://www.nabble.com/Page-instantiated-twice-tp22799162p25982806.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
