Hi,

I'm having a weird problem deploying my Wicket application in BEA. I only
manage to view the Application's HomePage and mounted BookMarkablePages.
Whenever I try to move from one of these pages (including a failed login
from the HomePage, which does not do 'setResponsePage', so it should load
the HomePage again), I get a PageExpiredException. Using Jetty everyhting is
fine.

I'm using Wicket 1.3.5. Debugging the Wicket classes I found out the root of
the problem is found in Session.getPage(final String pageMapName, final
String path, final int versionNumber).

The first difference I find when executing in Jetty and BEA is here
(Session.class line 694)

if (pageMapsUsedInRequest == null) {
                    pageMapsUsedInRequest = new HashMap(3);
}

With Jetty the variable does not have a null value (it is an empty Map).
With BEA, it is null.

Then, the execution is the same until it gets to the point: (Session.class
line 746)

PageMapsUsedInRequestEntry newEntry = new PageMapsUsedInRequestEntry();
newEntry.thread = Thread.currentThread();
newEntry.requestCycle = RequestCycle.get();
pageMapsUsedInRequest.put(pageMap, newEntry);
final String id = Strings.firstPathComponent(path,
Component.PATH_SEPARATOR);
Page page = pageMap.get(Integer.parseInt(id), versionNumber);
if (page == null)
{
pageMapsUsedInRequest.remove(pageMap);
pageMapsUsedInRequest.notifyAll();
}
else
{
// attach the page now.
page.onPageAttached();
touch(page);
}
return page;

In Jetty, it effectively returns a Page instance, but in BEA keeps returning
null.

Is there any setting I'm not aware of that may be causing this strange
behavior ? I use a custom session class (extending WebSession, and instanced
by means of Application.newSession), but do not override any of its
methods...

Thanks!
Xavier

Reply via email to