Re: [Wicket-user] page reloades infinitely

in 2.0 this is be default not a problem anymore. (the pagemap checker is disabled by default because it is not needed)Maybe if people do keep problems with this we should backport that change to 1.3 or something like that. johanOn 6/21/06, Matej Knopp [EMAIL PROTECTED] wrote: Yes, null is all

[Wicket-user] page reloades infinitely

Hi, I'm using firefox. when i duplicate a tab, the tab reloads in an infinite loop. this is the reason: script type=text/javascript!--//--![CDATA[//!-- var pagemapcookie = getWicketCookie('pm-nullwicket'); if(!pagemapcookie pagemapcookie != '1'){setWicketCookie('pm-nullwicket',1);} else

Re: [Wicket-user] page reloades infinitely

Strange. I'm looking into PageMapChecker#renderHead and it doesn't seem obvious why the generated url doesn't contain pageMap name. Are you using a custom URL encoding scheme or anything like that? -Matej Ittay Dror wrote: Hi, I'm using firefox. when i duplicate a tab, the tab reloads in

Re: [Wicket-user] page reloades infinitely

further investigation shows that for IE and openning new windows, it works fine - a PageMap instance is created, and the page loads fine. i've also started firefox with a new profile (no extensions), to make sure it's not extension related, and no, it happens there also, and also when i open a

Re: [Wicket-user] page reloades infinitely

Hmm.. The problem with this kind of bugs is that it's very difficult to reproduce. IMHO The problem is in this line: else {document.location.href = '/page/SomePage;jsessionid=E43E09C7B61190F3C8C5E98CB988F21F?';} The url should contain pagemap name (something like wicket-1). In wicket-1.2 the

Re: [Wicket-user] page reloades infinitely

Matej Knopp wrote: Strange. I'm looking into PageMapChecker#renderHead and it doesn't seem obvious why the generated url doesn't contain pageMap name. Are you using a custom URL encoding scheme or anything like that? yes about the custom schema. the page map name is mull. does it cause

Re: [Wicket-user] page reloades infinitely

Matej Knopp wrote: Hmm.. The problem with this kind of bugs is that it's very difficult to reproduce. IMHO The problem is in this line: else {document.location.href = '/page/SomePage;jsessionid=E43E09C7B61190F3C8C5E98CB988F21F?';} The url should contain pagemap name (something like

Re: [Wicket-user] page reloades infinitely

well, this is the code in WebRequestCodingStrategy: public final CharSequence encode(final RequestCycle requestCycle, final IRequestTarget requestTarget) { // first check whether the target was mounted CharSequence path =

Re: [Wicket-user] page reloades infinitely

ok, i did the same magic in my coding strategy and it works. in new tabs the url now looks like http://localhost/page/SomePage?wicket:bookmarkablePage=wicket-0:com.package.SomePage can someone explain the mechanism to me? also, why should i take care of this and not WebRequestCodingStrategy?

Re: [Wicket-user] page reloades infinitely

one other question. the original page map name is still 'null'. is this ok? Ittay Dror wrote: ok, i did the same magic in my coding strategy and it works. in new tabs the url now looks like http://localhost/page/SomePage?wicket:bookmarkablePage=wicket-0:com.package.SomePage can

Re: [Wicket-user] page reloades infinitely

Yes, null is all right. For every page the javascript checks, whether it's opened in new window/tab (therefore the cookie). If so, new pagemap is created, page is cloned into the new pagemap and the browser tab/window is redirected to the page in new pagemap). -Matej Ittay Dror wrote: one