I asked the EJB3 forum. The default expiration on SFSB is 300 seconds. There are custom JBoss annotations called @CacheConfig for both Simple and Tree caches which allow this to be customized on a per-bean basis.
This all may prompt some clarification in the Seam docs? My general notion of a SESSION scoped bean is that it is going to be around for the length of an HttpSession, period. This just isn't the case by default. Also, it seems to me that if people are using custom CONVERSATION timeouts greather than the 5 minute default, that they could run into the same situation where the timeout you're expecing from Seam/HttpSession is different than the timeout of the SFSB. Maybe Seam could implement some kind of "keep alive" annotated method on an SFSB to prevent the SFSB from getting expired out before its time? I'm not sure what the answer is across vendors, but I guess I'll try setting the @CacheConfig on every SESSION scoped bean to 1800 to match my HttpSession. Ryan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951299#3951299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951299 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
