if you click on a statefull link and on the server you don't do a redirect
the browser will show you that url
Or you do again a redirect to a mount, or you use ajax for those statefull
links.
johan
On 2/26/07, Peter Thomas [EMAIL PROTECTED] wrote:
Johan - the bookmarkable link in this case
yeah maybe we should because that those 2 really should be the same thing
if not then it doesn't work, so it invites bugs..
johan
On 2/25/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
mount(/item, new IndexedParamUrlCodingStrategy(/item,
ItemViewPage.class));
1) From looking at the above,
Would you care opening a JIRA issue for that Peter? Thanks.
Eelco
On 2/25/07, Johan Compagner [EMAIL PROTECTED] wrote:
yeah maybe we should because that those 2 really should be the same thing
if not then it doesn't work, so it invites bugs..
johan
On 2/25/07, Eelco Hillenius [EMAIL
Done: https://issues.apache.org/jira/browse/WICKET-326
About my other question about the URL remaining in place when navigating to
other pages, do you have any suggestions? Everything works fine and it is
just a minor irritance, but can't help wondering if I am missing some subtle
best practice
What do you mean? You click on a link and you don't want to update the url
thats in the browser?
Use ajax. Or use pages with versioning disabled
johan
On 2/25/07, Peter Thomas [EMAIL PROTECTED] wrote:
Done: https://issues.apache.org/jira/browse/WICKET-326
About my other question about the
Johan - the bookmarkable link in this case is within an email sent to the
user. It is not a big deal though and everything works fine. One way to
get things the way I want is to have all other links with that page
stateless and mounted. Since I do have non-stateless links, I was wondering
if
Hi,
I think the IndexedParamUrlCodingStrategy in Wicket and the way you use it
is really nicely done.
I have set up one as follows:
mount(/item, new IndexedParamUrlCodingStrategy(/item, ItemViewPage.class
));
1) From looking at the above, the mount path appears to be redundant. Is
there any
mount(/item, new IndexedParamUrlCodingStrategy(/item,
ItemViewPage.class));
1) From looking at the above, the mount path appears to be redundant. Is
there any particular reason
Nope, just the way it grew. We fixed that for for Wicket 2.0, but
didn't backport it. Maybe if there is enough
