Why are you building wicket in wicket?
Wicket keeps track of the last page already and detects back button
usage perfectly by itself.
Martijn
On Mon, Jun 16, 2008 at 1:26 PM, Eyal Golan <[EMAIL PROTECTED]> wrote:
> Hello,
> I have in my Session a field called pageId.
> I have Link that in the onClick I set in the session the page id and then go
> to a new page using setResponsePage.
> @Override
> public void onClick() {
> PortalSession session = ((SecuredBasePage)
> getPage()).getEurekifySession();
> session.setCurrentPageId(pageId);
> setResponsePage(pageClass, pageParameters);
> }
>
>
>
> In my base page's constructor I do this:
> ...
> String pageId = getEurekifySession().getCurrentPageId();
> LinksHeaderPanel linksPanel = new LinksHeaderPanel("linksPanel",
> pageId);
> ...
>
> everything goes well until I press the back button.
> When I press BACK button, naturally the Session still has the last pageId,
> because it is not set (to the old page id).
> Is there a way to fix this problem?
>
> *I cannot use PageParameters to keep the pageId.
>
> Thanks.
>
>
> --
> Eyal Golan
> [EMAIL PROTECTED]
>
> Visit: http://jvdrums.sourceforge.net/
> LinkedIn: http://www.linkedin.com/in/egolan74
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
