[
https://issues.apache.org/jira/browse/WICKET-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546444
]
Thijs Vonk commented on WICKET-1132:
------------------------------------
In my comment of 14-nov I said that I had to change something in the liferay
portal to get ajax support working.
Because of how Liferay works they would like the ajax requests to have the
'Accept' http header set to text/xml so that liferay knows what contenttype to
return in the response. I know wicket sets the contenttype in the response but
liferay checks the contenttype against the accept request header.
It's implemented a bit strange because they currently only read for wap.xhtml
otherwise only accept text/html. But it seems wicket would be the first
framework that actively return xml. (see
http://www.liferay.com/web/guest/community/forums/message_boards/message/299801
)
So i would like to propose a change to wicket-ajax.js so that when it does a
ajax request it also sets the 'accept' http header with 'text/xml'
> 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
>
>
> 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.
