just make sure that link has a popupsetting with a new pagemap
Then it works fine.
Currently it is a bit hard to detect that it is a real stateless page.
Because we do the most things in the head part of the page. But the problem is
that we only know if a page is stateless when it is first rendered ...(so at the end)
johan
On 5/5/06, Marco Geier <[EMAIL PROTECTED]> wrote:
I'd like to supress the PageMapChecker -headerscript for my statless pages.
Imho checking for new browser-window is not necessary for a stateless
page, but anyway this should be configurable (I'm still on wicket
1.2RC2, so forgive me if this has been made configurable in the meantime).
My scenario is this:
User clicks on a thumbnail and a new browserwindow pops up showing the
original-sized image. This page is stateless and bookmarkable and the
calling link has some query params ("?id=12345&class=foo"). These params
get lost during the NewBrowserWindowListener-Requestcycle and my page
fails to initialize the second time.
Anyway for performance reasons i'd like to avoid this additional cycle.
Rgds,
Marco
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
