Hello,
I developed a portlet which gets called on condition via <liferay-portlet:runtime portletName="2903"></liferay-portlet:runtime> inside another portlets view.jsp
Explanation: PortletA::view.jsp does check which Theme is currently applied and then either loads PortletB or keeps processing its own code.
It's a mobile version of the message boards portlet and does work on Tomcat 7.0.27 which I use for development.
Problem: The live server is Websphere and after the deployment process all links that were created with renderURL taglib don't work, e.g. after a click the same page just gets reloaded and nothing happens. The tags look like this:
Observed:
The posted snippet does produce a working link on Tomcat but not on Websphere. When I use <portlet:actionURL>instaed of <portlet:renderURL> it also works on Websphere.
When I add the portlet individually/directly into a page the renderURL do work again, but then I lose my condition which portlet should be loaded.
I believe it has something to do with some config rights for creating/calling renderURL of portletB inside portletA. I didn't find any viable solution for this issue.
Does anyone know a solution or a workaround?
Kind Regards,
Denis Dik
I developed a portlet which gets called on condition via <liferay-portlet:runtime portletName="2903"></liferay-portlet:runtime> inside another portlets view.jsp
Explanation: PortletA::view.jsp does check which Theme is currently applied and then either loads PortletB or keeps processing its own code.
It's a mobile version of the message boards portlet and does work on Tomcat 7.0.27 which I use for development.
Problem: The live server is Websphere and after the deployment process all links that were created with renderURL taglib don't work, e.g. after a click the same page just gets reloaded and nothing happens. The tags look like this:
<portlet:renderurl var="editURL">
<portlet:param name="struts_action" value="/mobile_message_boards/edit_message" />
<portlet:param name="redirect" value="<%= currentURL %>" />
<portlet:param name="messageId" value="<%= String.valueOf(message.getMessageId()) %>" />
</portlet:renderurl>Observed:
The posted snippet does produce a working link on Tomcat but not on Websphere. When I use <portlet:actionURL>instaed of <portlet:renderURL> it also works on Websphere.
When I add the portlet individually/directly into a page the renderURL do work again, but then I lose my condition which portlet should be loaded.
I believe it has something to do with some config rights for creating/calling renderURL of portletB inside portletA. I didn't find any viable solution for this issue.
Does anyone know a solution or a workaround?
Kind Regards,
Denis Dik
