anyway, I will continue investigating what's going on and file a bug report
if I can build a reproduceable case.
thanks
On 4/21/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
no that call will still remove the page from the session and delete all entries out of the pagemap stack.
Please add a bug report for this with a reproduceable case.
johanOn 4/21/06, Ingram Chen <[EMAIL PROTECTED]> wrote:getPageMap().remove(page) is no longer work in 1.2rc2...
I do not get expired error page when I back to explicitly removed page.
Is recent pageMap refactoring broken this feature ?On 1/28/06, Ingram Chen <[EMAIL PROTECTED]> wrote:yeh, it works now !
Thanks !On 1/28/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:ok plugged that.
-IgorOn 1/27/06, Ingram Chen <[EMAIL PROTECTED] > wrote:I tried getPageMap().removePage(this) and found one critical problem:
After I explicitly remove page, then navigate through 4~5 pages I got below exception:
27-01-06 22:58:53,563 ERROR wicket.protocol.http.WebRequestCycle -
java.lang.NullPointerException
at wicket.PageMap.remove(PageMap.java:310)
at wicket.session.pagemap.LeastRecentlyAccessedEvictionStrategy.evict(LeastRecentlyAccessedEvictionStrategy.java:83)
at wicket.PageMap.put(PageMap.java:463)
at wicket.Session.touch(Session.java:588)
at wicket.Page.doRender(Page.java:367)
at wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:143)
Can you help to check this ?On 1/27/06, Ingram Chen < [EMAIL PROTECTED]> wrote:I will check it when anonymous CVS ready !
Thanks a lot !On 1/27/06, Igor Vaynberg < [EMAIL PROTECTED] > wrote:ok what i did is add PageMap.removePage(Page)
which should be sufficient for your needs.
you can do Session.getPageMap(name).removePage()
or from within the page getPageMap().removePage(this) although i havent tried doing this one myself.
let me know if it works for you.
-Igor
On 1/26/06, Igor Vaynberg <[EMAIL PROTECTED] > wrote:sounds reasonable to me. if you would like you can add an rfe for it, but i should be able to get to it tonight at some point.
-Igor
On 1/26/06, Ingram Chen <[EMAIL PROTECTED] > wrote:My usecase is to prevent the user back to the previous page to submit
stale data:
page A with form --> the user submits ---> page B show success message
if the user navigate back to page A, and resumit page A again, he should get a expired
page.On 1/27/06, Igor Vaynberg < [EMAIL PROTECTED]> wrote:we are not against adding that back, but we would love to hear the usecase first.
the eviction strategy is much more flexible/poweful now and we were hoping it would be able to cope with most usecases.
-Igor
On 1/26/06, Ingram Chen <[EMAIL PROTECTED] > wrote:I upgrade to Latest 1.2 HEAD but found that session.remove() is
removed... I used to use this method to explicitly remove page instance:
getSession().remove(getPage())
How do I do this now ? Any suggestion ?
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen
