You would need both as there can be many different suppliers of a given ComponentType (DataSources are one example) that could have significantly different templates. I know we setup a compile time view of each component type in the console layer, but we need the flexibility to have a template keyed by a name. If we were to provide a lookup by ComponentType, I suppose we would have to add a notion of the preferred template so the template registration layer, or just provide a name to ComponentType mapping as part of the ManagementView bean configuration. The latter is the better approach. So I will add a feature request for the ManagementView.getDefaultTemplate(ComponentType componentType) api. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220092#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...