Hmm. In org.jboss.seam.portlet.PortletSessionImpl.java it says
| public Object getAttribute(String key)
| {
| return session.getAttribute(key);
| }
|
| public void setAttribute(String key, Object value)
| {
| session.setAttribute(key, value);
| }
|
|
which according to the Javadoc
http://docs.jboss.org/jbportal/spec/docs/javax/portlet/PortletSession.html#getAttribute(java.lang.String)
gets/puts the attributes in PORTLET_SCOPE which is defined to be portlet
private only. And the APPLICATION_SCOPE is portal "wide" scope.
Maybe in Seam we need new context APPLICATION_PORTLET_SCOPE (or PORTAL_SCOPE)
that uses the Portlet APPLICATION_SCOPE for storage. (
http://docs.jboss.org/jbportal/spec/docs/javax/portlet/PortletSession.html#APPLICATION_SCOPE
). IMHO the portlet APPLICATION_SCOPE name is causing some naming conflits and
should be renamed to PORTAL_SCOPE in the spec.
Or just simply hard code and change the PortletSessionImpl to always use the
(portlet) APPLICATION_SCOPE.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973112#3973112
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973112
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
