I say we should not attach lifecycle from one SFSB to another. You don't know where a
reference ends up and I can always come up with a scenario in which it breaks (we
haven't even covered handles yet).
The bean developer should be responsible for both parent and child lifecycle. We can
always have orphaned SFSB, because that's the nature of the beast.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008165#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...