[
https://issues.apache.org/struts/browse/WW-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44186#action_44186
]
Nils-Helge Garli commented on WW-2679:
--------------------------------------
As mentioned, there is minimal Struts 2 involved in this example. It simply
delegates to the underlying JSR168 implementation. So this simple example
should work. It would be nice if you could provide a minimal portlet war
example that illustrates the problem.
> Portlet session APPLICATION_SCOPE does not work between two portlet
> communication.
> ----------------------------------------------------------------------------------
>
> Key: WW-2679
> URL: https://issues.apache.org/struts/browse/WW-2679
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Portlet
> Affects Versions: 2.1.2
> Environment: Windows XP, Jetspeed 2.1.3, JDK 1.5_10, Eclipse 3.3.1
> Reporter: Alexander Leonov
>
> I was try to change the portlet example checking interportlet communication
> and found it is not work. For example:
> In first portlet action source:
> PortletActionContext.getRequest().getPortletSession()
> .setAttribute(ExchangeDispatcher.QUERY_NAME_SEARCH,
> getSearchQuery(),
> PortletSession.APPLICATION_SCOPE);
> and in second portlet action source:
> String query = (String) PortletActionContext.getRequest()
> .getPortletSession()
> .getAttribute(ExchangeDispatcher.QUERY_NAME_SEARCH,
> PortletSession.APPLICATION_SCOPE);
> In first portlet this session object are available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
