[
https://issues.apache.org/jira/browse/WICKET-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548667
]
Ate Douma commented on WICKET-1132:
-----------------------------------
Yes and no.
This concerns the handling of a ResourceURL request by the portal (see
ResourceURLFactory).
The ResourceURLFactory is based upon the JSR-286 features, correct.
In Jetspeed we already supported Ajax based requests (just AFAIK Liferay does)
and for that we also allow/support setting ServletResponse headers (just as
ResponseType, etc.)
So, in Jetspeed it was rather easy to implement the ResourceURL handling
internally.
For Liferay you really need to investigate their custom url//request handling
for Ajax stuff etc. and see if/how you can piggy-back the ResourceURL handling
on top of that.
I would at least expect Liferay support some kind of proprietary url handling
targetted at one portlet with full control over the response (as Ajax support
needs).
> 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.
