Re: [Springframework-developer] SimplePortletFormController changes

[J.Enrique R. <er...@di...>]

Hi Rainer,

I think that it isn't a feature :) The specification says:

-----

A portlet can bind an object attribute into a |PortletSession| by name. 
The |PortletSession| interface defines two scopes for storing objects:| 
APPLICATION_SCOPE and ||PORTLET_SCOPE|

All objects stored in the session using the |APPLICATION_SCOPE| must be 
available to all the portlets, servlets and JSPs that belongs to the 
same portlet application and that handles a request identified as being 
a part of the same session. Objects stored in the session using the 
|PORTLET_SCOPE| must be available to the portlet during requests for the 
same portlet window that the objects where stored from. Attributes 
stored in the |PORTLET_SCOPE| are not protected from other web 
components of the portlet application. They are just conveniently 
namespaced.
-----

I understand that '|PORTLET_SCOPE| must be available to the portlet 
during requests for the same portlet WINDOW ...' and '|PORTLET_SCOPE| 
must be available to the portlet during requests for the same portlet 
INSTANCE ...' are the same thing.
As you are using "request.getPortletSession().getAttribute("..")" and 
the API says that this method returns the object with the specified name 
for the |PORTLET_SCOPE, it could be there is a bug on your portlet 
container.|

Regards.

> One problem (or is it a feature?) remains: if there are two instances 
> of the portlet at the same page, both will get the form execution 
> result in the render request and thus will display the same content. 
> I've found no way to namespace encode the request property use for the 
> result forwarding. If anyone has an idea...
>
> I'll append the changed code to this message. Feel free to use it or 
> give any comments.
>
> Cheers
> Rainer


-- 
J.Enrique Ruiz
er...@di...
DISID, S.L.L.