[
https://issues.apache.org/jira/browse/WICKET-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144245#comment-13144245
]
Peter Pastrnak commented on WICKET-4019:
----------------------------------------
thank you, for the tagit.
i'm thinking about rewriting the portlet support, to not use the wicket filter
at all and copy some of the functionality to the wicket portlet (that can be
generalized later, if possible).
i don't see any reason, why do we have to use dispatcher.include at all, as we
could create the request cycle directly in the portlet. any idea why was it
done this way? there will be for sure some problems with package visibility,
but this is resolvable. and we might loose the option to access url parameters
generated by a javascript completely, but this is not allowed by the portlet
spec anyway, so we should solve it different way.
> 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
