Thanks for the quick replies.
Upgrading to 1.3 is only an option of last resort, as this only an
isolated example from a full application that is close to going live...
I've set getPageSettings().setAutomaticMultiWindowSupport(true); in
my application's init() method just to make sure.
I'v seen a redirect happen occasionally, but most of the time there
is none.
If I got it right wicket uses some javascript to do the redirect if
the window's name is empty and the set a name on that window?
So it probably will only work in a newly opened window/tab, right?
Is there a quick way to get the pagemaps and their contents for the
current session to see what's actually in them?
And where can I check/set the pagemap size?
Thanks for the help,
-markus
Am 21.03.2008 um 17:52 schrieb Johan Compagner:
yes it should be in 1.2
in 1.3 its not needed anymore so it should come from 1.2...
On Fri, Mar 21, 2008 at 5:51 PM, Igor Vaynberg
<[EMAIL PROTECTED]>
wrote:
was multiwindow support in 1.2? i dont remember anymore. basically
what is happening is that you open the page in two different windows
but they are in the same pagemap. so you can click 10 times in one
window - what that will do is push 3 older pages ( i think by default
pagemap size is 7) , including the one opened in another tab, out of
the pagemap. so when you go to click on the window in the other tab
you get page expired error.
-igor
On Fri, Mar 21, 2008 at 9:33 AM, Johan Compagner
<[EMAIL PROTECTED]>
wrote:
do you have new browser window detection enabled?
for example do you see an extra redirect happening when you open
the
page in
another tab?
this has to happen in 1.2 better is to upgrade to 1.3
johan
On Fri, Mar 21, 2008 at 3:12 PM, Markus Strickler
<[EMAIL PROTECTED]>
wrote:
Hi-
I have a simple form with some required fields set as homepage
for my
application.
Now if I open this page in 2 tabs of the same browser and just hit
submit in the two tabs I get Page Exipred pages.
This seems to happen rather randomly, sometimes on the first submit
click sometimes it takes 10 ore more clicks.
There is no error in the log file.
I've set logging to DEBUG and get this after i click on submit:
2008-03-21 15:10:06,040 DEBUG [wicket.Session] - <updateSession():
Attaching session to PageMap [PageMap name=null, access=[[Access
id=0, version=0]]]>
2008-03-21 15:10:06,041 DEBUG [wicket.Session] - <Getting page
[path
= 1:newsForm, versionNumber = 0]>
2008-03-21 15:10:06,042 DEBUG
[wicket.request.compound.DefaultEventProcessorStrategy] -
<commencing
event handling for [EMAIL PROTECTED]
pageClass=wicket.markup.html.pages.PageExpiredErrorPage]>
....
Is this expected behavior? Any hints on how to debug Page Expired
problems in general?
This is on wicket 1.2.6
Thanks for any help,
-markus
-------------------------------------------------------------------
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
