"adrian(a)jboss.org" wrote : We'll have to agree to differ then. ;-) | | P.S. I was planning on writing my own Swing admin console that was entirely | driven by the hints in the ManagedObjects. It might not be pretty, but it will | test whether the information/model can be used to construct "reasonable" UI | for user written deployers whose metadata model we know nothing about. I don't know that I so much disagree as don't want to get too hung up on making this a required feature initially. Certainly in principle the default jmx console could use this to generate a much better default view of the admin capabilities. Its just not a required feature in order for an admin tool to be able to effectively manage a server. I guess the main issue is validating that there are not incompatible evolutions of existing properties, as well as making sure that new properties that need user attention have some support without the tool needing a complete revision. For the ha datasource URLDeliimeter property, its is a new datasource type that does effectively need some synchronization with the admin tool as there can be a lot of hidden complexity in the list of jdbc urls in terms of a tool providing testing to ping the indicated databases. Arguably this also requires a new multi-valued jdbc url property rather than a separator that is used in combination with the old jdbc url. How we deal with this type of evolution best is the question. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067960#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...