To document our chat:
In 4.2 it works like this:
BeanA is the parent of a nested SFSB hierarchy. It holds a ref to the BeanB SBC (and to
the XPC). The "one serialized unit" you mention is passivated under BeanA.id.
When BeanB is passivated, what gets written to disk under BeanB.id is a
ProxiedStatefulBeanContext; a proxy. If the user activates BeanB, the
ProxiedStatefulBeanContext is activated and knows how to find BeanA's cache, find the
BeanA SBC in that cache, and find the real BeanB SBC inside the BeanA SBC. The
ProxiedStatefulBeanContext then delegates all calls to the real BeanB SBC.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082191#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...