[ 
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.1.1.zip

Version 1.5.1 was based on wrong branch, so it did not include changes from 
1.5.0. This one should be a correct merge (the only changed class was the 
MarkupIdPrepender). We will run some tests today and tomorrow.
I've noticed, that some components with ajax behaviour add a parameter to the 
generated resource url, that is not accessible using 
Request.getQueryParameters, only by getPostParameters or getRequestParameters. 
The reason is that the method call getQueryString and getParameterMap of 
PortletServletRequestWrapper are inconsistent. I guess there was the same 
problem in version 1.4.
We've experienced this problem in TagIt component, that uses 
Request.getQueryParameters method. Similar component - Autocomplete in 
wicket-extensions works fine, as it uses Request.getRequestParameters. The 
solution could be that the PortletServletRequestWrapper  would merge parameters 
from the url with wicket resource url parameters. Maybe I'll find some time 
next week to investigate a little more and fix it, because this makes some 
components unusable.
                
> 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: ResponseState.java, Wicket - Portlet.htm, 
> wicket-portlet-1.5.0.zip, wicket-portlet-1.5.1.1.zip, 
> wicket-portlet-1.5.1.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

        

Reply via email to