Jan (et al), I just started reading the JSR-88 spec, and yes--I'll be happy to implement a JSR-88 tool to plug into the console. This spec describes exactly what I was thinking about.
I'm refactoring the console app to be more modular and pluggable. A lot of the work for this is presently taking place. I'm probably going to abstract out the raw JMX client console stuff into its own module as well. This shouldn't be difficult--this sort of pluggability is exactly what shocks is designed for ; ) Thanks for pointing me at this. I've been thinking about it since August--I think Richard mentioned functionality like this in the very very early days of the project, but I never investigated it in full. Now I grok the JSR-88 stuff. I'll keep you all posted on this. -- N. Alex Rupp ([EMAIL PROTECTED]) ----- Original Message ----- From: "Jan Bartel" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 20, 2003 2:46 PM Subject: Re: Demo at ApacheCon > Norm, > > I think this kind of thing is what JSR88 is all about. It assumes that > 3rd parties will provide such configuration tools that generate DDs for > an app and handle part of the app lifecycle (distribute, deploy etc). > App server vendors provide a JSR88 api implementation that plugs into > these 3rd party tools in a standard way. Are you suggesting that > Geronimo provides it's own JSR88 tool via the web console? > > Jan
