I think this is a very cool idea and would solve this entire class of problems. I think the problem is this will not be easy to implement. I suggested the ServiceBindingManager service, because it was the simplest thing I could think of to fix the port problem.
May be this will be easy to add to the JMX html adapter Scott just added. BTW, Scott where did you get the code. Jules, how are you going to find just the port attributes from the services? -dain Scott M Stark wrote: > So write a prototype to demonstrate the beauty of this approach. > We need something yesterday. > > 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 5:42 AM > Subject: [JBoss-dev] Slice-n-Diceable JMX HTML Adaptor views.... > > > >>I posted this as a followup to a thread on jboss-user - no-one commented >>on it. >> >>I think it is a neat idea, so I'm reposting it, under it's own subject >>just in case no-one noticed it last time... >> >>The context mentioned a BindingService which appears to be being written >>to hand out ports to services, to make it simpler to run multiple JBoss >>instances on one box.... >> >>------------------------------------------------------------------------- >> >>I've been thinking about ports and other configuration issues. >> >>This goes back to the mega-thread about whether configurations should >>all be stored together, or not. >> >>Scott has hinted at a future omniscient/persistant JMX-based >>configuration mechanism. >> >>It seems to me that all these problems could be solved by taking >>different JMX HTML Adaptor 'views' across all the services. >> >>For ports you simply have a PortView page, which is configured to list >>all the ports. >> >>No doubt you will also need a files/directories/urls view and several >>others. >> >>These views could be configured in xml and would be far more flexible >>than hard-wiring a service for each view. Furthermore they would not >>require any further integration work on the part of the service. >> >>Users could configure their own views. You could have novice/expert >>views etc.... >> >>Finally any JMX based approach to this would integrate straight into >>whatever Scott has planned, whereas a BindingService will be yet another >>service to configure..... >> >>Comments ? >> >> >> >>Jules >> >> >>P.S. >> >>I guess we just need a JMX view servlet which has access to a number of >>configuration files (.jxml?). When you hit one, it just renders the JMX >>view... - simple !! >> >> >>_______________________________________________________________ >> >>Don't miss the 2002 Sprint PCS Application Developer's Conference >>August 25-28 in Las Vegas - >> > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - >http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
