Matej Knopp schrieb:
hi matej
mount the page using HybridUrlCodingStrategy.
i already did.
The url for page instance (you can use PageLink for that) will than look
like /foo/document/21.5 (where .5 denotes page instance). Note that
such url *is* bookmarkable, the page instance number
you have to encode the necessary state yourself into the page
parameters. There is no way for Wicket to be able how to serialize the
state in the URL in some magic way.
Martijn
On Fri, Aug 1, 2008 at 9:41 AM, Uwe Schäfer [EMAIL PROTECTED] wrote:
Matej Knopp schrieb:
hi matej
mount the page
Page remembers the original page parameters with which it has been
created. So when you use PageLink (with an existing page instance) the
parameters will be there.
If you want to change the parameters you can try Page#getPageParameters().
-Matej
On Fri, Aug 1, 2008 at 10:46 AM, Martijn Dashorst
Martijn Dashorst schrieb:
you have to encode the necessary state yourself into the page
parameters. There is no way for Wicket to be able how to serialize the
state in the URL in some magic way.
kind of misunderstanding here. i dont want or need the additional state
bookmarkable.
all i want
what i now want to add is to pass additional state
You can not do this with a BookmarkablePageLink. The trick is to create
a Link with in the onClick something like:
// note the variant that accepts a Class argument does not work:
setResponsePage(new Page(), pageParameters)
// the redirect will
Hi
following situation:
i have a link to a page, that has to be bookmarkable, say:
/foo/document/21
where FooPage is mounted at/foo
no problem here, but: coming from page XY i´d like to pass additional
data to the foopage, normally done with construction, while i need the
url still to be
Hi,
mount the page using HybridUrlCodingStrategy.
The url for page instance (you can use PageLink for that) will than look
like /foo/document/21.5 (where .5 denotes page instance). Note that
such url *is* bookmarkable, the page instance number doesn't matter.
Unfortunately wicket has to store
