Behrang Saeedzadeh

JSF-based JSR-168 Portlets are broken

Thursday, October 5, 2006 2:49:53 PM

So the other day we easily solved the Redirect-after-Post problem in a JSP-based JSR-168 Portlet.

This time I was trying to figure out how to solve this in a JSF-based (to be more precise, JSF 1.1) Portlet, but so far I have not found a workaround. The <redirect /> hint also didn't help (at Least in Liferay 4.1.2.)

Can we safely conclude that JSF-based JSR-168 Portlets are simply broken!?

RAP in JSR-168 PortletsEifffel...

Comments

Unregistered user # Thursday, October 5, 2006 9:43:53 PM

Julien Viet writes: Try with JBoss Portal that implements redirect after post.

Behrang Saeedzadehbehrangsa # Friday, October 6, 2006 12:36:50 PM

Julien,

I just browsed through the JSR 168 specification once again and couldn't find anywhere a statement saying that the portal must RAP processActions...

Unregistered user # Friday, October 6, 2006 12:52:25 PM

Subbu Allamaraju writes: Well, there is no requirement for the aggregating app to do redirect after a POST - it is an implementation choice. It all depends on how the aggregating app manages its own state.

Behrang Saeedzadehbehrangsa # Friday, October 6, 2006 1:23:28 PM

Subbu,

Won't this lead to a Portlet not resubmitting the form content after a browser refresh in a container, and resubmitting it in another one? Shouldn't this be precisely specified by the spec?

Regards,
Behi