Seems weird... First of all, it won't be freed up until the session is invalidated or the app takes it out of the session context. Then, I'm not too sure how it will behave wrt activation/passivation.
I think the web layer also does its own bit of passivation/activation and writes objects in the session context to disk (depending on configuration)... maybe this is different when you're running tomcat inside of a J2EE container but I'd rather not muck with that :) Anyway, I think the real reason is that it's cleaner to think of the web layer as a "client" of the EJB container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912500#3912500 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912500 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
