Hi,
It's working nicely on Tomcat.
I'll have to rectify on what I've said on the first assertion. With Jetty,
the first time I try, pageMapsUsedInRequest is null too. I'll try to provide
a more elaborate description of the things happening in the second code
fragment...
I've tried even to remove weblogic.xml to bypass any harmful setting I could
have in it, but it's still happening the same. Curious thing is, I remember
seeing it work before. By the way, I'm on BEA 9.2 MP3,
I'd be grateful to any hint that could lead to this problem's solution
(thanks Igor).
Cheers!
Xavier
2009/11/13 Igor Vaynberg <igor.vaynb...@gmail.com>
> try in tomcat. sounds like bea is not tracking your sessions.
>
> -igor
>
> On Fri, Nov 13, 2009 at 7:37 AM, Xavier López <xavil...@gmail.com> wrote:
> > 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
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
"Klein bottle for rent--inquire within."
