the SFSB  is a good idea except JNDI.

JNDI is not meant to scale according to your user number. In addition when a 
statefull bean is evicted it would not be unbound from the JNDI tree and you 
would have to make some garbage by yourself.

Try with JBoss treecache which can be either replicated or local, using the 
user ID as key. You can specific an eviction policy and it can be replicated. 
And actually now http session replication is using treecache to replicate its 
session (JBossCacheSessionManager).

"schnelzer" wrote : I have come up with a approach for communication between 
portlet applications and I would like to get some feedback.  My requirements 
are:
  | 
  | *  a session that is visible across portlet applications
  | *  an approach that will work well in a clustered environment (Julian, I 
couldn't easily see how to extend a static map so I started down an alternate 
path)
  | 
  | 
  | What I plan to do is create a Stateful Session Bean for each active user 
during login. When the Session Bean is first created, I will put the remote 
reference in the JBoss naming directory using the user's ID as the key.  
Portlets that need to read or update attributes that cross portlet applications 
will lookup the remote reference using JNDI and interact with the user's 
instance of the Session Bean.  I believe this approach will behave well in a 
cluster since JNDI and Stateful Session Beans are well supported in a JBoss AS 
cluster, right?
  | 
  | Any feedback is appreciated.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873530#3873530

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873530


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to