Re: [Mc4j-development] remote logging interface

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

There can be multiple conditions, but they are only "and"
conditions... such that only MBeans matching all the conditions will
be selected.

All the MBeans in the server will be tested for these conditions so
you can match as you like. You can also set the BeanMatch type to be
"multiple" in order to find lists of MBeans matching all conditions.
Or alternately, you can have more than one BeanMatch tags in order to
bind different MBeans to different "id"s.

The only documentation is the brief, Dashboard Guide available at:
http://mc4j.sourceforge.net/dashboard-dev/DashboardXML.html

Mostly, you'll create swing Components that implement one of
org.mc4j.console.dashboard.components.BeanComponent
org.mc4j.console.dashboard.components.BeanListComponent

The first being for components using the BeanMatch type="single" and
the second being for lists of beans using BeanMatch type="multiple".

There is no special listener support at this point though I am open to
suggestions on the dashboard model and its flexibility. To be honest,
the jmx notification system is a little too weak to support using the
built in notification nodes for getting notifications, so it would
probably be best to just register a local notification listener for
the mbean that is sending the log notifications. If you want, I'll see
if I can hook up my old code to that sort of thing to display the
notifications.

For now, you can watch the notifications by simply browsing to the
MBean providing them and right-clicking on the notification sub-node
and selecting "Listen".

On Fri, 28 Jan 2005 14:41:03 -0600, James Rosen <jam...@gm...> wrote:
> Anything you could send me would be great.  I'm trying to develop a
> dashboard for it, but I can't find any documentation on writing
> dashboards.  I gather that MBeans are included in the dashboard
> through the
> <BeanMatch id="MBeanNode" type="Single">
>   <Condition type="BeanObjectNameCondition" filter="type=Threading" />
> </BeanMatch
> tags, but I'm not sure of the details.  Can I have multiple
> conditions?  If so, how are they combined?  Does a dashboard
> automatically look for all beans and filter on conditions, or does it
> have to be feed the MBeans?
> Is the only way to add swing event handling to include it in the class
> itself, or is there a way to just create some listeners and add them
> to the classes via the dashboard xml?
> 
> Is there any documentation on this stuff?  If not, I imagine I'll
> start documenting as I go; how should I organize it?
> 
> -James
> 
> 
> On Tue, 25 Jan 2005 22:59:36 -0500, Greg Hinkle <gre...@gm...> wrote:
> > That's a great idea. I'm not sure how quickly notifications can be
> > sent, but as long as the logging level isn't too detailed the
> > notifications idea could work.
> >
> > I've actually got a UI for a remote log viewer I built a while back
> > that might be a start for the display of the messages if I can find
> > it. And a setLogLevel interface would be great. Feel free to pitch in
> > any or all of this as you'd like.
> >
> > On Tue, 25 Jan 2005 08:55:54 -0600, James Rosen <jam...@gm...> wrote:
> > > I am working on porting the ui of some java processes to JMX, and
> > > would like to view logging information in real-time (well, slightly
> > > delayed real-time).  I couldn't find a way to watch log statement
> > > occur from JConsole or from MC4j, so I was wondering whether this was
> > > already in the works or whether I should add the feature.
> > >
> > > My proposal:
> > > -a JMXAppender, compatible with Log4j which sent notifications to a
> > > listener in the MC4J console
> > > -a console-side listener which posts messages to a JTextPane; there
> > > would be options for maxMessageHistorySize, etc.
> > > -a more user-friendly version of the setLoggingLevel property of the
> > > log in view, perhaps?
> > >
> > > -James
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > > Tool for open source databases. Create drag-&-drop reports. Save time
> > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > > _______________________________________________
> > > Mc4j-development mailing list
> > > Mc4...@li...
> > > https://lists.sourceforge.net/lists/listinfo/mc4j-development
> > >
> >
> > --
> > Greg Hinkle
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > Tool for open source databases. Create drag-&-drop reports. Save time
> > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > _______________________________________________
> > Mc4j-development mailing list
> > Mc4...@li...
> > https://lists.sourceforge.net/lists/listinfo/mc4j-development
> >
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Mc4j-development mailing list
> Mc4...@li...
> https://lists.sourceforge.net/lists/listinfo/mc4j-development
> 

-- 
Greg Hinkle