7 messages in org.apache.wicket.usersRe: Could not find component after se...| From | Sent On | Attachments |
|---|---|---|
| Francois Meillet | Mar 14, 2012 4:51 am | |
| Martin Grigorov | Mar 14, 2012 5:50 am | |
| François Meillet | Mar 14, 2012 6:14 am | |
| Martin Grigorov | Mar 14, 2012 6:18 am | |
| Francois Meillet | Mar 14, 2012 6:49 am |  .zip |
| Martin Grigorov | Mar 15, 2012 2:43 am | |
| Francois Meillet | Mar 15, 2012 3:20 am |
| Subject: | Re: Could not find component after session dies | |
|---|---|---|
| From: | Martin Grigorov (mgri...@apache.org) | |
| Date: | Mar 14, 2012 6:18:29 am | |
| List: | org.apache.wicket.users | |
2012/3/14 François Meillet <fmt...@meillet.com>:
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 <qqzz...@gmail.com> 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
-- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
-- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com