does the bookmarkable url change? is it still exactly where you first go too?johanOn 8/1/06, Justin Lee <
[EMAIL PROTECTED]> wrote:-BEGIN PGP SIGNED MESSAGE-Hash: RIPEMD160
I'm up to date onhttps://svn.sourceforge.net/svnroot/wicket/branches/WICKET_1_2I *am* using a bookmarkable link to ge
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I'm up to date on
https://svn.sourceforge.net/svnroot/wicket/branches/WICKET_1_2
I *am* using a bookmarkable link to get to the page, fwiw.
Eelco Hillenius wrote:
> Which version are you using Justin?
>
> Eelco
>
>
> On 8/1/06, Johan Compagne
Which version are you using Justin?
Eelco
On 8/1/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> are you saying that your page is created twice?
> This can happen if it was a bookmarkable request. But the window.name
> (1.2.1) or wicket cookie (1.2)
> check did a redirect to your page. Because
are you saying that your page is created twice?This can happen if it was a bookmarkable request. But the window.name (1.2.1) or wicket cookie (1.2)check did a redirect to your page. Because it noticed that you have opened another window (or wrongly noticed)
johanOn 8/1/06, Justin Lee <[EMAIL PROTEC
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Yeah. I don't do anything to the render strategy. I have break points
set in my page constructor and various model objects and I'm seeing the
flow stop at those break points multiple times before the page gets
rendered. I have to go meet with a
please give us a test case. Normally a page is only rendered once.What kind of Renderings Strategy do you use? the default one?johanOn 8/1/06,
Justin Lee <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-Hash: RIPEMD160I'm seeing my page get processed twice which is causing some problem
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I'm seeing my page get processed twice which is causing some problems.
Granted some of those problems are likely design issues which I'm
addressing, but as a result I'm seeing two session objects get created.
Is that double processing a result of
