great ! Thanks Martin
Le 15 mars 2012 à 10:43, Martin Grigorov a écrit : > https://issues.apache.org/jira/browse/WICKET-4454 > > On Wed, Mar 14, 2012 at 3:49 PM, Francois Meillet > <[email protected]> wrote: >> Hi Martin, >> >> Here is the code (maven project) >> >> François >> >> >> >> >> >> Le 14 mars 2012 à 14:18, Martin Grigorov a écrit : >> >>> 2012/3/14 François Meillet <[email protected]>: >>>> Hi Martin, >>>> >>>> Le 14 mars 2012 à 13:50, Martin Grigorov a écrit : >>>> >>>>> Hi Francois, >>>>> >>>>> On Wed, Mar 14, 2012 at 1:51 PM, Francois Meillet >>>>> <[email protected]> wrote: >>>>>> Release: >>>>>> Wicket 6.0-SNAPSHOT >>>>> >>>>> Good! >>>>> And sorry if I break the APIs from time to time ;-) >>>> ;-) >>>> >>>>> >>>>>> >>>>>> >>>>>> The pages: >>>>>> All pages extends a Skeleton, which has a header panel. >>>>>> >>>>>> In this header panel, another panel is displayed, depending if the user >>>>>> is logged (ConnectedPanel) or not (HeaderLoginPanel). >>>>>> >>>>>> So when a user is not connected, the component's structure is >>>>>> Page-HeaderPanel-HeaderLoginPanel >>>>>> and when the user is connected, the structure is >>>>>> Page-HeaderPanel-ConnectedPanel >>>>>> >>>>>> >>>>>> The problem: >>>>>> The user logs in and waits until the session die. >>>>>> Then when he clicks on link linktest >>>>>> (org.apache.wicket.markup.html.link.Link), in the ConnectedPanel , the >>>>>> following error appears: >>>>>> >>>>>> Could not find component 'HeaderPanel:HeaderLoginPanel:linktest on page >>>>>> 'class HomePage >>>>>> >>>>>> Question 1 >>>>>> Why does Wicket try to find linktest in the HeaderLoginPanel ? >>>>>> As Linktest belongs to ConnectedPanel. >>>>> >>>>> Can you check what is the url in the produced html (view page source). >>>>> It will be even more weird if the link url is correct but later Wicket >>>>> confuses itself somehow. >>>> >>>> Not a good new : the url is >>>> <a wicket:id="linktest" >>>> href="./?2-1.ILinkListener-HeaderPanel-HeaderLoginPanel-linktest">linktest</a> >>>> The problem is the same with the 1.5.5 >>> >>> It is a good news for me. That means the problem is somewhere in your code. >>> Can you show the code ? >>> >>>> >>>>> >>>>>> >>>>>> Question 2 >>>>>> Why don't I get a PageExpiredException ? >>>>> >>>>> Try with >>>>> org.apache.wicket.settings.IPageSettings#setRecreateMountedPagesAfterExpiry(false) >>>>> >>>> >>>> That works >>>> >>>>>> >>>>>> >>>>>> François >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Martin Grigorov >>>>> jWeekend >>>>> Training, Consulting, Development >>>>> http://jWeekend.com >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >>>> >>> >>> >>> >>> -- >>> Martin Grigorov >>> jWeekend >>> Training, Consulting, Development >>> http://jWeekend.com >>> >>> --------------------------------------------------------------------- >>> 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] > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
