About portlet replication:
by default JBoss Portal does not do anything and portlet session are wrappers of
HttpSession but of a *dispatched* session, quite often in a cross context manner.
We have an internal replication mechanism which leverages the portal session (i.e the one
we are sure it is replicated). To store portlet session state in the portal session to
have the replication feature. So we don't do much magic as we use standard Servlet API
and nothing else and everything we do seems to me valid.
So bottom line, we can do portal replication and optionally we provide a replication for
portlets that configures it. We don't use anything that is not Servlet API based and
that is not exotic.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168792#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...