You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Thijs Vonk (JIRA)" <ji...@apache.org> on 2007/12/05 14:33:43 UTC
[jira] Issue Comment Edited: (WICKET-1132) Liferay portlet support
[ https://issues.apache.org/jira/browse/WICKET-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548663 ]
thyzz edited comment on WICKET-1132 at 12/5/07 5:33 AM:
-------------------------------------------------------------
I've come across a issue with the ajax link redirect example.
If I'm reading the portlet 1.0 specs correctly a portal is not allowed to give the portlet access to the response headers. So setHeader/addHeader will have no effect. This is what happens in Liferay. If I set a header on the response it will be ignored and never sent to the client.
So the code httpServletResponse.addHeader("Ajax-Location", url) in WebResponse will have no effect.
Also the setHeader() calls to response in AjaxRequestTarget seem to be useless.
Ate how does JetSpeed/Pluto handle this? Or are you already using the 2.0 spec for this with the addProperty in the Mimeresponse?
was (Author: thyzz):
I've come across a issue with the ajax link redirect example.
If I'm reading the portlet 1.0 specs correctly a portal is not allowed to give the portlet access to the response headers. So setHeader/addHeader will have no effect. This is what happens in Liferay. If I set a header on the response it will be ignored and never sent to the client.
Ate how does JetSpeed/Pluto handel this? Or are you already using the 2.0 spec for this with the addProperty in the Mimeresponse?
> Liferay portlet support
> -----------------------
>
> Key: WICKET-1132
> URL: https://issues.apache.org/jira/browse/WICKET-1132
> Project: Wicket
> Issue Type: Bug
> Components: wicket-portlet
> Affects Versions: 1.3.0-beta4
> Environment: Liferay 4.3.3 on Tomcat 6
> Reporter: Thijs Vonk
> Assignee: Ate Douma
> Fix For: 1.3.0-rc2
>
> Attachments: patch-jira-wicket-1132.patch
>
>
> I created 2 simple Links a AjaxLink and a 'normal' link in a portlet. I deployed this portlet on Liferay. The normal link works fine. But the Ajax links doesn't work. In the generated HTML the url's look like this.
> AJAX link:
> <a href="#" wicket:id="link" onclick="var wcall=wicketAjaxGet('http://localhost:8080/web/guest/admin?p_p_id=MiniPortlet&p_p_action=1&p_p_col_id=column-1&p_p_col_count=1&',null,null, function() {return Wicket.$$(this)}.bind(this));return !wcall;" id="id__MiniPortlet__WAR__MiniPortlet1____link1">
> Normal link:
> <a href="http://localhost:8080/web/guest/admin?p_p_id=MiniPortlet_WAR_MiniPortlet1&p_p_action=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1&_MiniPortlet_WAR_MiniPortlet1__wu=%2Fminiportlet%2F%3Fwicket%3Ainterface%3D%3A0%3Alink2%3A%3AILinkListener%3A%3A" wicket:id="link2">
> At this moment the p_p_id is the part that I'm looking into. As you can see they are different. And for Liferay this part tels it which portlet it should send the request to. The normal link is the correct path to the portlet. as this action actually works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.