&quot;charles.crouch(a)jboss.com&quot; wrote : | | 4) We need the concept of a deployment type in order to support retrieving all ManagedObject's/deploymentName's of a particular type e.g. DataSource | | either | public List<ManagedObject> getViews(ProfileKey key, DeploymentType deploy) | | throws NoSuchProfileException, IOException | | | or | | | public List<String> getDeploymentNames(ProfileKey key, DeploymentType deploy) | | throws NoSuchProfileException, IOException | I think we need to flesh out the ManagedObject to deployment metadata mapping issue to define this. The ManagedPropertyRef I had previously dealt with the notion of a collection of properties using the context notion: | public class ManagedPropertyRef | { | /** | * A namespace context that maps the managed property onto a managed view | * context (e.g., /, /DataSource, /DataSource/Pool). | */ | private String context; | Part of the property mapping definition should be a classification of the property from the perspective of an admin tool. In reality a property may be in multiple view/perspectives if we start talking about view likes "Server Ports", "Clustering", "Network Interfaces". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995705#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...