"adrian(a)jboss.org" wrote : | There should be no merging for display to the user, that would | be pointless. | | e.g. If the default DataSource is set in the metadata | at the deployment level or server level you don't want to merge this into the | ejb instance view. | The user cannot change the global default value by modifying a | single ejb. | | This default metadata is in a seperate deployment. | | The only merging would be explaining to the user where a | particular value came from and potentially providing a unified | editiing tool that explains to them that they are either changing | a global default or they are overriding it for their particualr | deployment, instance, etc. The issue is illustrated by the enc example in that multiple scopes and sources of metadata go into the object that is used to create the javax.naming.Context that will be installed for a given component enc context. The default DataSource does need to get merged (resolved is a better term, maybe that is the confusion) into the cmp2 metadata. If I have not specified it via an annotation or descriptor, it has to be picked up from an encompassing scope. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974865#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...