You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Pastrnak (JIRA)" <ji...@apache.org> on 2012/07/04 14:32:35 UTC

[jira] [Updated] (WICKET-4019) Portlet Support 1.5

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

Peter Pastrnak updated WICKET-4019:
-----------------------------------

    Attachment: wicket-portlet-1.5.7.2.zip

This time a tested fix for the multipart support (last one did not work properly). The whole problem is, that wicket javascript library adds "wicket-ajax-*" parameters to the form action (instead of headers), so we have to include these parameters in the wicket url when doing the include.
Martin, thank you for the detailed description. I have commited the latest sources to github (core-1.5.x).
                
> Portlet Support 1.5
> -------------------
>
>                 Key: WICKET-4019
>                 URL: https://issues.apache.org/jira/browse/WICKET-4019
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>    Affects Versions: 1.5-RC7
>            Reporter: Peter Pastrnak
>         Attachments: PortletServletRequestWrapper.java, ResponseState.java, Wicket - Portlet.htm, wicket-1.5.2.1.zip, wicket-portlet-1.5.0.zip, wicket-portlet-1.5.1.1.zip, wicket-portlet-1.5.1.2.zip, wicket-portlet-1.5.1.3.zip, wicket-portlet-1.5.1.4.zip, wicket-portlet-1.5.1.5.zip, wicket-portlet-1.5.1.zip, wicket-portlet-1.5.2.2.zip, wicket-portlet-1.5.2.4.zip, wicket-portlet-1.5.2.zip, wicket-portlet-1.5.5.0.zip, wicket-portlet-1.5.5.1.zip, wicket-portlet-1.5.7.1.zip, wicket-portlet-1.5.7.2.zip, wicket-portlet-1.5.RC7.zip, with bind(this).jpg, without bind(this).jpg
>
>
> Url returned by the RequestMapper does not seem to be properly rendered, as it does not encode question mark character in the Url parameter value (I haven't checked the w3c spec, but at least Liferay Portal seems to require it to be encoded) 
> The reason is this definition in the UrlEncoder: 
>                         case QUERY : 
>                                 // to allow direct passing of URL in query 
>                                 dontNeedEncoding.set('/'); 
>                                 // to allow direct passing of URL in query 
>                                 dontNeedEncoding.set('?'); 
> Currently URL "http://host/file?param=a?b" would be encoded as "http://host/file?param=a?b", instead of "http://host/file?param=a%3Fb"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira