I find this a bit interesting because in my experience, @PageLink has
ignored my session scoped data (it is not session-aware), which kept
resulting in NPEs (and the nasty exception page for users) on my
navigation links when the session timed out (all of my pages use session
data to render). My workaround for that was to switch everything to use
@DirectLink and call a silly listener method:
public String gotoPage(String pageName)
{
return pageName;
}
And then in the .html:
<a href="#" jwcid="@DirectLink" listener="listener:gotoPage"
parameters="literal:Home">...</a>
I don't know if such a technique would be helpful for you or not (I've
not used client-side persistence).
/dev/mrg
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Callender
Sent: Monday, April 03, 2006 10:27 AM
To: [email protected]
Subject: Why does PageLink include state in the URL?
When my page has @Persist("client") on some properties, the state
becomes
included in the URL of PageLinks. eg.
<a href="/perspectives/app?page=web%2Fmain%
2FTestsPage&service=page&state:Home=BrO0ABXcOAAAAAQAAB3N0cmluZ3
NzcgATamF2YS51dGlsLkFycmF5TGlzdHiB0h2Zx2GdAwABSQAEc2l6ZXhwAAAA
A3cEAAAACnQABUZpcnN0dAAGU2Vjb25kdAAFVGhpcmR4">PageLink</a>
Does this serve a purpose?
The problem is that when the URL becomes too long then the link fails
silently.
But all I want to do is go to a different page with a link on the
navigation bar,
regardless of the data on the current page.
Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
