You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2007/09/12 15:30:32 UTC

[jira] Resolved: (WICKET-924) New Wicket Portlet support: Support non-relative urls in Ajax.Request redirect callback handling

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

Ate Douma resolved WICKET-924.
------------------------------

    Resolution: Fixed

> New Wicket Portlet support: Support non-relative urls in Ajax.Request redirect callback handling
> ------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-924
>                 URL: https://issues.apache.org/jira/browse/WICKET-924
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket, wicket-portlet
>    Affects Versions: 1.3.0-beta3
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>
> As portlets don't have real urls but are served within the context of the portal application, the default behavior of Wicket to generate request relative URL is rewritten (for portlets) to generate context relative urls again.
> The Wicket.Ajax.Request.stateChangeCallback function currently only expects request relative URLs and makes them fully qualified itself too.
> For portlet support this the stateChangeCallback function needs to verify if the url already is fully qualified or context relative first before trying to making it qualified.  

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