geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "n. alex rupp" <>
Subject Re: [newbie] JMX Console - where to start?
Date Wed, 03 Sep 2003 21:23:06 GMT

If you're anxious to get started on twiddle commands for a CLI, you could
start working on them today and host them at service-cache. I intended it to
be a sort of "input filter" for the project--a place for people to
collaborate and try stuff out before they submit it to Geronimo (that way
even newbies can get CVS access and start working on code, trying out and
developing their ideas or just spin their wheels if they want).

If you want to build a twiddle-commands subproject there, let me know : )
If you'd rather just manage your own SF project, that's cool too.

N. Alex Rupp (

----- Original Message -----
From: "Matthew David Kurjanowicz" <>
To: <>
Sent: Wednesday, September 03, 2003 2:47 PM
Subject: Re: [newbie] JMX Console - where to start?

> As far as Twiddle commands go, I think that we should try to mirror
> closely the actions taken in any management console (or consoles).  So if
> we decide to write Twiddle commands, we need to make sure that what Alex
> is working on will do the same thing (like start server, etc.) -> if there
> are more than one way to start and stop a server.  I think this should be
> spread to a higher level, and that we should decide to represent objects
> the same way on different consoles.  (i.e., a server, a Database, Database
> pool, should be represented the same way in Twiddle, vs. on the web, vs.
> in a Swing window).
> That said, I am extremely willing to begin working on Twiddle commands.
> Also, once Alex gets more code out about his web console, I'd like to port
> some of it to a Swing console -> this being bc of my preference of Swing
> over web, but it's just a personal preference (and I can host it and work
> on it somewhere else if need be).
> Just 2cents.
> -Matt
> > On Wed, 3 Sep 2003, Dain Sundstrom wrote:
> >> Aaron,
> >>
> >> Alex was working on the exact kind of tree you are suggesting, and I
> >> asked him to hold off on it until he had the basic JMX console stuff
> >> working, because we need a console so bad.
> >
> > OK.  Do you want to (add and/or) identify some of the console
> > goals on the Wiki page as being particularly urgent?  It sounds like
> > there's enough interest to put some Twiddle commands together as well.
> >
> >> He is using pure JMX, but I don't know what you mean by "will the same
> >> JSR-77 components be available?"
> >
> > Let me quote Gianni, when he was talking about how all the JSR-77
> > components were exposed through the MEJB:
> >
> > "More accurately, the manageable objects may or may not be MBeans, in
> > our case they will be (Dynamic) MBeans, and should not be accessed
> > directly. One should use the MEJB home anrd remote interfaces to
> > interact with them as MBeans."
> >
> > So if you're supposed to use EJB interfaces to interact with the
> > JSR-77 components, and the web console operates strictly through JMX (no
> >  MEJB), will the web console have full access to the JSR-77 components
> > exposed through the MEJB (because they're Dynamic MBeans in our
> > implementation), or will they be effectively hidden from the JMX view
> > because it doesn't know about the MEJB?
> >
> > Aaron

View raw message