&quot;bill.burke(a)jboss.com&quot; wrote : Adrian, I'm not grokking here... See the scoped metadata in org.jboss.metadata in the container project and its integration with the MC which was discussed/done within the last couple of months. anonymous wrote : | | | | | <bean name="bar/> | | </scope | | That won't work because you define the scopes hierarchically but also somewhat randomly (even without introducing session/thread/transaction/converstation/etc. :-) e.g. You can have a bean scope myapplication/mydeployment1/mybean1 myapplication/mydeployment1/mybean2 myapplication/mydeployment2/mybean1 But you also want to be able to define it in code, e.g. adding beans to a subsystem scope which isn't part of a deployment but deployments can be in that subsystem. e.g. I know this part of the jca code goes in the jboss-jca subsystem scope | @org.jboss.metadata.scope.Subsystem("jboss-jca") | public class MyJCAImplementationObject {} | So it needs to be abitrary scope annotations against the bean (and the deployment for convenience). anonymous wrote : | Kernel app= kernel.createScope("Application"); | Kernel session = app.createScope("session"); | Yes, you need to be able to create a child kernel see my point (1) in the first response, but you also need to add it to the MetaData scope otherwise how does somebody which kernel to use in an abitrary context. That is the purpose of the MetaData/MetaDataStack. NOTE: This is all very speculative since besides maintaining the MetaDataRepository yourself in some code none of this exists. i.e. there is nothing that says I want to deploy this metadata into this scope. That is what I meant before when I said: "Although I think a more general notion would come out of the work we need to do to define scoped metadata". The repository exists with all the plumbing, but there is nothing to fill it! :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008952#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...