You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/03/11 04:00:10 UTC

[jira] Resolved: (WICKET-86) Stateless components everywhere breaks existing applications

     [ https://issues.apache.org/jira/browse/WICKET-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eelco Hillenius resolved WICKET-86.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

> Stateless components everywhere breaks existing applications
> ------------------------------------------------------------
>
>                 Key: WICKET-86
>                 URL: https://issues.apache.org/jira/browse/WICKET-86
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3
>            Reporter: Martijn Dashorst
>         Assigned To: Martijn Dashorst
>             Fix For: 1.3
>
>
> In our application we just upgraded to 1.3, and the stateless components break urls on bookmarkable pages.
> These are url's generated on a DataView#Item, using component.urlFor(ILinkListener.INTERFACE);
> 	CharSequence urlForLink = LinkItem.this.urlFor(ILinkListener.INTERFACE);
> 	return "javascript:location.href='" + urlForLink + "';";
> Wicket 1.3:
> javascript:location.href='/vocus/app?wicket:bookmarkablePage=:nl.topicus.iridium.web.gui.leerling.LeerlingZoekenPage&wicket:interface=:2:leerlingen:3::ILinkListener';
> Wicket 1.2:
> javascript:location.href='/vocus/app?wicket:interface=:3:leerlingen:3::ILinkListener';
> The 1.3 version doesn't work for paged requests. The default of setting the components to stateless breaks in this case our application.
> The workaround for this particular component is to override 'getStatelessHint()' and return false in it. However we are afraid more components will break silently.
> In the logs we see:
> 11:39:45,103 [http-8080-Processor24] INFO  wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveListenerInterfaceTarget(DefaultRequestTargetResolverStrategy.java:304) : component not enabled or visible, redirecting to calling page, component: null

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.