/**
* Gets the url that references this handler.
*
* @return the url that references this handler
*/
public CharSequence getCallbackUrl()
{
return getCallbackUrl(true, false);
}
calling this method:
public final CharSequence getCallbackUrl(final boolean recordPageVersion, final boolean onlyTargetActivePage)
if it was me then we do exactly the inverse:
return getCallbackUrl(false, true);
because for an ajax request you don't want page versioning and you do want to target only the active page (for i guess 90%+ of the time)
because ajax calls not on the active page don't seem very usefull to me and page versioning for ajax is also not very usefull
most of the time, because all other urls and forms still point to the old one. So the page will be rollbacked pretty often.
I just debugged a problem that uses the normal getCallbackUrl() where the had very vague problems about page expires.
This was happening because of the ajax request that was happening just right after a post. (onBlur)
So the ajax call didn't do the work in the active page but on another page in the pagemap..so the new page was thrown out.
This vague behaviour can happen to a lot of people because of these defaults we have, which in my eyes are wrong
but maybe i don't see all the cases.
johan
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
