"wolfc" wrote : I would rather have the SFSB register themselves as users in the
XPC. The XPC then maintains this list. On @Remove SFSB deregisters and if XPC is empty
close itself.
OK. But only parent context holds a ref to the XPC, yes? Otherwise you have the problem of
multiple contexts independently serializing/deserializing the XPC, after which you no
longer have a shared reference.
The XPC would need to know which context has the ref to it, so as part of the close
process it can inform that context it no longer needs to be cached. It's the caching
of the parent context that keeps the XPC from being gc'd. Unless we come up with a
separate cache for these.
Shit, if a call to a child bean triggers replication, the parent bean must be replicated
as well, otherwise the XPC isn't. Perhaps separately caching XPCs makes sense. :(
anonymous wrote : For injection: any SFSB with an XPC with creates a SFSB propagates the
XPC with the exception of @Remote. Hmm... still don't like it, but there is no other
way.
Not clear exactly what you mean here. :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008561#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...