]
Pete Muir reassigned JBSEAM-1557:
---------------------------------
Assignee: Wesley Hales
I think the JBoss Portlet bridge solves this. If so, please close the issue Wesley :)
Seam is peforming a redirect in when running as a portlet, rather
than using the portlet lifecycle
--------------------------------------------------------------------------------------------------
Key: JBSEAM-1557
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1557
Project: JBoss Seam
Issue Type: Bug
Components: Core, Portal
Affects Versions: 1.2.1.GA
Environment: WinXP / Liferay 4.3.0 / Tomcat 6.0.13
Reporter: Neil Griffin
Assigned To: Wesley Hales
Attachments: Manager.java
Background: I found this problem when attempting to package the Seam
"Registration" example as a portlet under Liferay Portal.
Section 7.4.2 of the JSF 1.1 specifcation says that since redirects are not possible in
the case of portlets. Nevertheless, the Seam Conversation Manager (Manager.java) is
forcing the portal to redirect outside its portal pages, rather than use the portlet
lifecycle.
The way this would be manifested to the user would be like this: If a Seam application
was contained within a portlet, and the portlet were placed on a portal page, then when
the user clicks on a button that invokes navigation to a different JSF view, then the Seam
application would "jump out" (so to speak) of the rectangular portlet container,
and become a full-browser-page thing. This is incorrect. If a Seam application starts out
as a portlet, then it must remain a portlet for its entire lifespan. In addition, the
current behavior of Seam is not conforming to section 7.4.2 of the JSF 1.1.
specification.
Now, it might be the case that this redirect works under JBoss Portal, but it causes
exceptions to be thrown under Liferay Portal. This is because Liferay Portal expects
JSF-based portlets to not perform redirects, as they must not do that anyway.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: