[
https://issues.jboss.org/browse/GTNPORTAL-1933?page=com.atlassian.jira.pl...
]
Vu Viet Phuong logged work on GTNPORTAL-1933:
---------------------------------------------
Author: Vu Viet Phuong
Created on: 21/Jul/11 4:07 AM
Start Date: 21/Jul/11 4:06 AM
Worklog Time Spent: 3 hours, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 3 hours, 30 minutes
Worklog Id: (was: 12424849)
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
Time Spent: 3 hours, 30 minutes
Remaining Estimate: 0 minutes
javax.portlet.actionScopedRequestAttributes do not seem to be functioning.
This blog post descibes what it should do:
http://wpcertification.blogspot.com/2011/02/actionscopedrequestattributes...
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