When services have their configuration seperated and available as an object or xml doc then this approach makes more sense. As described here the peristent state would have to be incorporated into the view definition or else I have no way of configuring server 2-N on a box. There is a chicken and egg problem in establishing a non-default configuration since I have to bring up the server to edit its properties through the html view.
The future of service management needs to address: - Seperating the configuration state from the service definition. - A persistence service that manages the access to a services configuration for a given JBoss server instance. This configuration info will be applied to a service in the same way that today the configuration embedded in the service definition is applied. - XML representations of a services configuration to allow for XSL based transformation from the peristence layer and service management consoles. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jules Gosnell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 13, 2002 3:29 PM Subject: Re: [JBoss-dev] Slice-n-Diceable JMX HTML Adaptor views.... > > Jules, how are you going to find just the port attributes from the > > services? > > > > I'm not. > > I'm going to assume that they can be set via JMX, and then I am going to > put an empty e.g. PortView.jmxl/jxml page into CVS and then when you add > a service that has a configurable port you will copy the template from > the top of the file and add you service's port.... > > Of course, initially, there would be a certain amount of research to put > togther pages for extant services, but I would expect the service > maintainer to add their JMX attributes to whichever views they > considered appropriate.... > > Thus keeping it simple.... > > If you can think of a way to generate these views dynamically - cool, > but I was thinking about statically maintained views - I know - a > maintenance nightmare - but at least it's only an xml template, not a > load of source code.... > > > What do you think ? > > > Jules > _______________________________________________________________ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
