When the rendering mode is set to redirect to buffer, the page gets
rendered problerly. But after it's displayed, you can't work it with, on
every interaction it shows the expired page. So it's not in pagemap.
so maybe the setResponsePage (resp. redirectTo) should explicitly put
the page into to the pagemap?
-Matej
Johan Compagner wrote:
yes but still i could hold a page somewhere. that i use as a response
page. some time in the further.
Then that page is rendered then can be out of the pagemap already (if
there are already make other pages between that time)
A page should be in front of the stack when it is used yes?
And when is it used? Currently the code says at 2 times:
creation (the Page.init())
when it is called from the outside (callComponentListener())
I also would say 2 times but creation is changed into rendered/when it
is the response page.
johan
Eelco Hillenius wrote:
Ah, no, I remember now. The page is put at front of the stack when it
is accessed. So, this should allways work. In fact when you look at
the name of the collection, it was a bug that it didn't until recently.
Eelco
Eelco Hillenius wrote:
Sounds logical, yes.
Eelco
Johan Compagner wrote:
if i look at the Call Hierarchy of PageMap.put(Page) then pages are
only added in there init()
or in the callComponentListener() this is wrong. A Page should be
put when it is rendered. (when it is the response)
I think that Page.init() isn't needed. A page only has to go in the
pagemap when it is the response page at one time.
Then it can be used as a page that can be it by a listener. Not before.
And if we add response pages to the pagemap (or resetting them) then
the problem Matej had is fixed.
johan
Eelco Hillenius wrote:
Thought this was fixed actually. Hmmm. Maybe after 1.0?
I'm sending you the current snapshot offline. Could you be so kind
and test
whether this is still a bug?
Cheers,
Eelco
Matej Knopp wrote:
Hi
I know I has already been discussed here but I'm not quite sure so
I'm asking again.
When I do this
setResponsePage(page);
setRedirect(true);
and the page instance is no longer in pagemap, shouldn't it be put
there? I'm using wicket 1.0 and it doesn't seem to do so.
When the policy is set to redirect_to_buffer, the page gets
rendered, but since it's not in pagemap, it can't be interact with
(expired exception).
I know there is a workaround
getPageMap().put(page)
but I'd just like to know if this is a bug or a feature.
Thanks.
-Matej
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
