Here's some notes I jotted down when looking at SEam: * Context/scope aware kernel - ability to define components and attach them to a scope - metadata would set in scope definition and not execute to expliclity created. - can inject between scopes. One scope can override another scope with bean definition. - almost "federated" but a little different as you can declare beans of different scopes in the same file. - maybe starting off with federation is the correct way. With a kernel having a parent and children kernels. - scope/context is a bit different than federation. You'd want the base template of the scope/context defined in bean.xml and you want to ask the kernel to create you a specific scope/context. So scope/context may be implemented via federation, but the kernel would have to know about the scope. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008893#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...