JBoss Portal 2.4.0 source org.jboss.portal.portlet.PortletRe

[vietanh.vu]

Hi everyone,

In this file, at line 210

 if (type == ACTION_TYPE)
 {
 this.navigationalstate = null;
 this.interactionState = query;
 this.form = form;
 }
 else
 {
 this.navigationalstate = query;
 this.interactionState = null;
 this.form = null;
 }

I don't know if the this.form is deliberately set to null in this case. It means that if the user requests the portlet in render mode, it will discard all form data. For example,

<form action="<portlet:renderURL/>" method="post">
 <input type="hidden" name="xxx" value="1"/>
</form>

when user submit this form, the xxx=1 will be discarded completely.

Is it a bug, or a feature?

http://vpensieve.blogspot.com/2006/12/jboss-portal-240-revisit.html

[theute]

Wrong forum.

You must not use request parameters in render mode only render parameters.

(And you should check before you blog)

Moving topic.

[vietanh.vu]

You must not use request parameters in render mode only render parameters.

Why I can't use request parameters in render mode? Is that documented somewhere in the JSR168? Please enlighten me.

[theute]

Because the render phase must have no side-effect.

And the JSR 168 tells that you cannot rely on obtaining the request parameters on render calls, only render parameters.

[vietanh.vu]

I found it

Thank you

[julien1]

Wowww... someone that diggs the code :-)

Yes actually it is discarded on purpose.

[julien1]

Actually I read several posts of your blog, in particular the POST/GET with form. Here is the main reason of why we don't want to have FORM+GET :

The problem of FORM GET is that there is no specification that says how the browsers should merge the parameters of the URL of the form to submit with the form fields.

As the portal may encode data in the URL parameters, depending on the browsers, those parameters may be discarded partially or completely and the portal request may not be able to occur.