[gatein-issues] [JBoss JIRA] Assigned: (GTNPORTAL-1933) actionScopedRequestAttributes not available for portlets

[Vu Viet Phuong (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vu Viet Phuong reassigned GTNPORTAL-1933:
-----------------------------------------

    Assignee: Vu Viet Phuong


> actionScopedRequestAttributes not available for portlets
> --------------------------------------------------------
>
>                 Key: GTNPORTAL-1933
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-1933
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Common integration
>    Affects Versions: 3.1.0-GA
>         Environment: Java6
>            Reporter: m l
>            Assignee: Vu Viet Phuong
>              Labels: portal-s57
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> javax.portlet.actionScopedRequestAttributes do not seem to be functioning.
> This blog post descibes what it should do:
> http://wpcertification.blogspot.com/2011/02/actionscopedrequestattributes-container.html
> They make possible to call request.setAttribute() from processAction() to RenderRequest, to be available in the PortletFilter.
> There is a workaround by using response.setRenderParameter(), but I have a portlet that is already working in Liferay and I'd like to port it to GateIn by having this feature available.
> I have this in my portlet.xml:
>   <container-runtime-option>
>        <name>javax.portlet.actionScopedRequestAttributes</name> 
>        <value>true</value> 
>   </container-runtime-option>
> Still those attributes I set in processAction get lost, and are not available by RenderRequest.getAttribute()

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira