There is no error. Just the generated url contains a state
(wicket:interface=.....) which means "use this page instance when the
user tries to open this Url".
Using setResponsePage(Class) has no state and creates a Url which when
targeted will create a *new* page instance.
On Wed, May 11, 2011 at 11:50 AM, Andrea Del Bene <adelb...@ciseonweb.it> wrote:
> Hi Carlo,
>
> what kind of error/exception do you get when you use "setResponsePage(new
> ConfirmPage())"? Does it work if you use "setResponsePage(
> ConfirmPage.class);"
>
>> Hi There,
>>
>> I'm mounting bookmarkable pages in the Wicket Application. For example,
>>
>> mount("index", IndexPage.class);
>> mount("confirmPage", ConfirmPage.class);
>>
>> I'm quite successful when using the following code
>>
>> setResponsePage(IndexPage.class);
>>
>> http://localhost:8080/application/index
>>
>> However,
>> when I try to use
>> setResponsePage(new ConfirmPage());
>>
>> http://localhost:8080/application/?wicket::::<1>::
>>
>>
>> It doesn't work already.... Is there anyway that I could workaround this?
>> It appears as something like this.
>>
>> Thanks
>> Carlo
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
