[
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.2.2.zip
1.5.2.2. - last version here, next week i'll switch to wicketstuff. We
definitely need some unit tests, in the last version (1.5.2.1) i tried to fix
the GET vs. POST parameters problem with parameters added by javascript (found
in TagIt), but it broke too many other things. It does not seem to be easy to
reconstruct the original querystring, so i better leave this for now, as it was
(as this is most probably container dependent). That means the parameter will
be in the parameterMap, but not in the querystring and Wicket will recognize
these parameters as POST parameters.
I have to check this in the spec, but I guess, that correct solution might be
to prefix all these parameters with the portlet namespace, because normally you
should not have access to these parameters at all.
Martin, if you could change the TagIt component to accept both types, it would
be the best.
> 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.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
