[
https://issues.apache.org/jira/browse/WICKET-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123405#comment-13123405
]
Peter Pastrnak commented on WICKET-4019:
----------------------------------------
ronny, about the precondition problem. if you are sure that everything works
without the portlet container (and wicket portlet), then just try to find the
difference between the generated htmls (with and without the container), that
causes the problem. the differences should be mainly in the generated IDs and
URLs, so usually the problem is that either one of the javascript libraries is
not loaded or browser cannot correctly interpret the url / id. But you should
use the wicket-portlet 1.5.1 version, as the previous versions have IDs for all
tags.
thats why i suggested to disable the MarkupIdPrepender, because then you shoul
dhave the same IDs as without the portlet container. The only differences will
be in the URLs. Also check if there is the same problem using any browser (I
would test it f.e. on firefox first with firebug plugin enabled, that you see
all the errors and unloaded libraries).
> 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.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
