|
| I've a portlet application written using IBM API that's been working in WPS4 and 5 (with some modifications). Now when I deploy it on WPS 6, it looks that PortletSession.setAttribute/getAttribute methods act as if in application scope not in portlet scope
anymore.
It seems that each portlet gets/sets the same configuration object from the session. The code is like this {in init() method}:
PortletSession pos = portletrequest.getPortletSession();
Object otqb = pos.getAttribute(SESSION_ATTRIB_QUERY);
if (otqb == null) {
tqb = new TQueryBean(portletrequest, portletresponse);
pos.setAttribute(SESSION_ATTRIB_QUERY, tqb);
}
All portlets are configurations of the same base portlet, so there is just one portlet class. It last ran correctly on WPS 5.0.2 -- each portlet initialized it's own configuration. Now in WPS 6 it looks like each next portlet finds the configuration (TQue
ryBean) initialized by the other portlet.
Any ideas what could go wrong? I cannot specifically indicate scope when using IBM API, right? Could there be some parameter in WPS settings to exclude portlet scope (this happens on my test server)
|
|