| Summary: | PortletBridge doesn't handle session timeout properly | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Matt Wringe <mwringe> |
| Component: | Portal | Assignee: | Nobody <nobody> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.2.1.GA | CC: | epp-bugs |
| Target Milestone: | --- | ||
| Target Release: | 5.2.x | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-1487 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Matt Wringe
2012-01-24 16:07:47 UTC
Link: Added: This issue depends GTNPORTAL-2332 When a portlet serveResource() call throws an exception, the portal ignores the exception and the portal page acts as if nothing happened. A possible workaround is for the portlet, or Portlet Bridge, to catch the exception and call the following to set the HTTP response code for the Browser: this.resp.setProperty(ResourceResponse.HTTP_STATUS_CODE, Integer.toString(status)); The original problem relating to Session timeout triggers this scenario because a JSF portlet throws a ViewExpiredException on Session timeout. It's worth noting that this error doesn't occur on Session timeout when the user is not authenticated. The general integration issues of the portal and portlets around exceptions and proper handling is intended to be addressed by Julien for GateIn 4.0, which would mean changes to EPP 6. |