As described, I'm not seeing much distinction between a scope and a subcontext. Espcially for the case of the enc handling, this would seem to be more of a metadata scope with the key and scope set at runtime by an enc aspect. For a invocation, the enc aspect queries for the enc context created during deployment starting at the instance level, and finds it at different levels depending on the deployment type. Fleshing out simple resusable aspects and associated deployers for things like an enc, security and logging for kernel beans is what we should look at to flesh this out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971458#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...