"charles.crouch(a)jboss.com" wrote : "scott.stark(a)jboss.org" wrote : | | 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". | | | | I'm not sure I fully understand this. Take for example two properties on a DataSource: the jndiName, and maxConnectionPoolSize. Would both of these properties get mapped to the /DataSource context? | Say I had two datasources deployed A and B, and I searched specifying the "/DataSource" context, would I get four property instances back? Two jndiName's and two maxConnectionPoolSize's? How would the jndiName and maxConnectionPoolSize for DataSource A get linked? | The querying of the view has not been defined. If it was a tree "DataSource/{Pool,Security}" and you asked for the DataSource tagged properties, you should get all. If you asked for the DataSource/Pool properties, you would only get the pool oriented properties. If we want to query across deployments by view (and that certainly makes sense for many view, DataSources included), then yes, we should be returning 4 properties tied back to the 2 ManagedObjects for the 2 deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995757#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...