[
https://issues.apache.org/jira/browse/PB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927539#action_12927539
]
Alexey Zavizionov commented on PB-109:
--------------------------------------
I think the sequence is normal to the portlet spec.
Attribute looks "shared", you are right. I fixed it. [1]
"The one "quirky" feature of the Struts Bridge is that it, as a Portlet 1.0
based solution, needs the custom
org.apache.portals.bridges.common.ServletContextProvider interface
to access the ServletContext from a Portlet and invoke Struts through it. With
Portlet 2.0 this no longer would be needed but the Struts Bridge hasn't been
adjusted for that. "
hmm, we have own implementation of ServletContextProvider. Does it really not
need?
It doesn't work well yet.
Can you try our test application?
-------
[1] PLT.11.1.4 Request Attributes
Request attributes are objects associated with a portlet during a single
portlet request.
Portlets can not assume that attributes are public between action, resource,
event and
render requests.
> 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]
