Thanks, I tried that but I get an exception in the Wicket 1.3
snapshot I'm using. Is there a known bug in the remove(Page)
method? Or maybe I'm simply using it wrong? (after logging in, my
secured page is attempting to invoke loginpage.getpagemap().remove
(loginpage) in the secured page's
yes thats a know bug, i think matej did fix that today or is fixing it right
now.
johan
On 9/12/07, Justin Morgan (Logic Sector) [EMAIL PROTECTED] wrote:
Thanks, I tried that but I get an exception in the Wicket 1.3
snapshot I'm using. Is there a known bug in the remove(Page)
method? Or
Hi Matej,
i think matej did fix that today or is fixing it
Any word on whether this bug is fixed? (see stack trace below)
Or should I file a JIRA issue if there's not one already?
Many thanks,
Justin
On Sep 12, 2007, at 5:50 AM, Johan Compagner wrote:
yes thats a know bug, i think matej
It should be fixed in svn already.
https://issues.apache.org/jira/browse/WICKET-942
-Matej
On 9/12/07, Justin Morgan (Logic Sector) [EMAIL PROTECTED] wrote:
Hi Matej,
i think matej did fix that today or is fixing it
Any word on whether this bug is fixed? (see stack trace below)
Or
Hi,
Okay, another newbie question. :)
I have some secured pages that require a user login. The main page
(unsecured) has direct links to these secured pages. If the user
tries to access one of these secured pages without being logged in, I
throw a restartresponseexception that takes
