No, portlet session are portlet-local. There is no standard way to do
inter-portlet communication in the portlet spec, but most products provide some
proprietary APIs.
It is something I need to look into more closely with Roy.
View the original post :
http://www.jboss.com/index.html?module=bb&
It that true for Seam applications? I thought that Seam was a bit close to
JBoss Portal. I have read different places that JBoss Portal supports
interportel communication if they are build into the same portlet application.
Quote:
"Any object stored in the session using the APPLICATION_SCOPE is
Sorry for answering myself!
Now I've found a way to solve my problem. It works when I use the
PortletSession and the APPLICATION_SCOPE. Now I have also found the way to get
the PortletSession from Seam:
((javax.portlet.PortletRequest)
getFacesContext().getExternalContext().getRequest()).getPor
I have a roadmap item to look at integrating JBoss Portal's IPC stuff with
Seam. But I have not done any of the research I need to do to understand this
stuff properly yet.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951919#3951919
Reply to the post :
ht
Yes in Portal per the spec there are 2 scopes of session, portlet and
application scope.
Currently in Seam we only support Portlet scope.
IPC is different, it doesn't have any context, it just trigger events that
other portlets are listening to.
View the original post :
http://www.jboss.com
Originally, I had actually planned a PORTLET_SESSION scope distinct from the
SESSION scope. But then from Roy I got the impression that use of the global
session scope was considered a Bad Thing. Perhaps we need to revisit that
discussion.
On the IPC stuff, it is an event architecture, and so i
SESSION scope is misused to do IPC in a standard way (It's the only way that
would work on any JSR168 portlet container).
There is no real logic for application session scope.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951944#3951944
Reply to the post :
Well, I guess I'm just not quite convinced that this is always a misuse...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952072#3952072
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952072
__
I thought I'd seen a portlet scope, that is PortletSession.APPLICATION_SCOPE
reservation in earlier seam documentations and wondered what has happened when
the time came for it to be used.
I'd rather be "misusing" session with Seam annotations than doing it
"by-the-book" without Seam support.