[
https://issues.apache.org/jira/browse/PB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924322#action_12924322
]
Ate Douma commented on PB-109:
------------------------------
Hi Alexey,
Sorry for a late response but yes: Struts bridge does work well with more than
one portlet (instance) on a page.
The (potential) problem with multiple Struts bridge portlets is that it uses
(and has to use) the Servlet/Portlet Session to pass on parameters, even if
only temporarily.
As a dispatched servlet (as the StrutsServlet) doesn't "know" about
PortletSession.PORTLET_SCOPE, all session attributes by default end up in the
shared APPLICATION_SCOPE, hence potential interference between multiple
instances.
For the Struts bridge running on a portlet 1.0 container, this can be "fixed"
by setting the optional StrutsPortlet init parameter
portletScopeStrutsSession=true, which activates the (bridges common)
ServletPortletSessionProxy to be used.
See also PB-49
When running on a portlet 2.0 container, this behavior is now part of the spec
itself (see: PLT.10.4.3) and can be enabled by defining
container-runtime-option javax.portlet.servletDefaultSessionScope=PORTLET_SCOPE
for the portlet.
Either one of the above solutions should fix your problem.
> Problem with the request wrapper (user action is not considered)
> ----------------------------------------------------------------
>
> Key: PB-109
> URL: https://issues.apache.org/jira/browse/PB-109
> Project: Portals Bridges
> Issue Type: Bug
> Components: struts
> Affects Versions: 1.0.4
> Reporter: Ali Hamdi
> Priority: Minor
>
> We found a bug in Struts Portals bridge reported here :
> http://jira.exoplatform.org/browse/PC-512
> The fix done by eXo developer is here :
> http://jira.exoplatform.org/secure/attachment/25968/diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
