As we discussed, I can work around this for Session scoped SFSB's by using the JBoss specific @CacheInfo annotation, setting the timeout to be the same as an HttpSession.
But what about Application scoped SFSB's? We run into this same problem due to the aforementioned reasons in this thread. An Application scoped SFSB should be viable for the lifetime of an application... but it isn't, and setting a ridiculously large timeout using @CacheInfo would only delay the problem. JBoss times these out like any other SFSB, throws an EJBNoSuchObjectException, and Seam can't recover. Since EJBNoSuchObjectException is a standard ejb exception, is there a way that Seam could gracefully recover from this? This all (this thread) seems to me to be quite critical to the promise of Seam -- my component instances should be around for the lifetime of the scope context specified. Ryan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952196#3952196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952196 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
