[
https://issues.apache.org/jira/browse/WICKET-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122937#comment-13122937
]
Peter Pastrnak commented on WICKET-4019:
----------------------------------------
is it problem for every Ajax based component? I've tried to compare one of our
'orderBy' elements with yours but I could not find any difference. The ID of
the element is, in my opinion, defined correctly and is the same as the one in
Wicket.$(). Were all the Wicket Javascript libraries loaded correctly in your
case (I guess they are, if it works) ?
/poc-portlet/projectList/ps:NDI3NjI1OWQtYjE5OC00YmU2LTk1ODUtYWI1ZTFiOTU3MjVi/wicket/resource/org.apache.wicket.markup.html.WicketEventReference/wicket-event-ver-1316958366000.js"
/poc-portlet/projectList/ps:NDI3NjI1OWQtYjE5OC00YmU2LTk1ODUtYWI1ZTFiOTU3MjVi/wicket/resource/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax-ver-1316958366000.js"
/poc-portlet/projectList/ps:NDI3NjI1OWQtYjE5OC00YmU2LTk1ODUtYWI1ZTFiOTU3MjVi/wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/wicket-ajax-debug-ver-1316958366000.js"
YOUR 'orderBy' component:
<a
href="/rpo/public/edp/applications/wicket?portal:componentId=4276259d-b198-4be6-9585-ab5e1b95725b&portal:type=action&interactionstate=JBPNS_rO0ABXdvAANfd3UAAAABAFsvcHJvamVjdExpc3QvPzM3LTEuSUxpbmtMaXN0ZW5lci10YWJsZS10b3BUb29sYmFycy10b29sYmFycy0yOC1oZWFkZXJzLTItaGVhZGVyLW9yZGVyQnlMaW5rAAdfX0VPRl9f"
wicket:id="orderByLink"
id="G4276259d_2db198_2d4be6_2d9585_2dab5e1b95725b_orderByLinkc0b2"
class="wicket_orderUp"
onclick="var wcall=wicketAjaxGet(
'/rpo/public/edp/applications/wicket?portal:componentId=4276259d-b198-4be6-9585-ab5e1b95725b&portal:type=resource&portal:resourceID=/projectList/?37-1.IBehaviorListener.1-table-topToolbars-toolbars-28-headers-2-header-orderByLink&portal:cacheLevel=PAGE&portal:windowState=normal&portal:portletMode=view',
function() { }.bind(this),function() { }.bind(this),
function() {
return
Wicket.$('G4276259d_2db198_2d4be6_2d9585_2dab5e1b95725b_orderByLinkc0b2')
!= null;
}.bind(this)
);
return !wcall;"
>
OUR 'orderBy' component:
<a
href="/portal/ecare/-/wellcome?p_auth=jfam95sK&p_p_id=EcareWelcomePortlet_WAR_ecareportlet&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-3&p_p_col_count=1&_EcareWelcomePortlet_WAR_ecareportlet__wu=%2FEcareWelcomePortlet%2F%3F3-1.ILinkListener-welcomeContainer-invoiceComponent-content-head~id-sortBy~id"
title=""
class="tablebuton_up tablebuton_up"
wicket:id="sortBy-id"
id="_EcareWelcomePortlet_WAR_ecareportlet__sortBy_id5b"
onclick="var wcall=wicketAjaxGet(
'/portal/ecare/-/wellcome?p_p_id=EcareWelcomePortlet_WAR_ecareportlet&p_p_lifecycle=2&p_p_state=normal&p_p_mode=view&p_p_resource_id=%2FEcareWelcomePortlet%2F%3F3-1.IBehaviorListener.1-welcomeContainer-invoiceComponent-content-head~id-sortBy~id&p_p_cacheability=cacheLevelPage&p_p_col_id=column-3&p_p_col_count=1',
function() { }.bind(this),
function() { }.bind(this),
function() {
return
Wicket.$('_EcareWelcomePortlet_WAR_ecareportlet__sortBy_id5b') !=
null;
}.bind(this)
);
return !wcall;"
>
> 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
>
>
> 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