This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 59843 - Provide a module API for JConsole
Summary: Provide a module API for JConsole
Status: NEW
Alias: None
Product: contrib
Classification: Unclassified
Component: JMX (show other bugs)
Version: 5.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: Jean-francois Denise
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-10 15:03 UTC by Jean-francois Denise
Modified: 2005-06-10 15:03 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-francois Denise 2005-06-10 15:03:36 UTC
From matt stevens (Matthew.stevens@sun.com)
"Is there an API on the JMX support module where I could execute the 
"start JConsole" action with a connection parameter.  Just thinking 
outloud here.  I am not aware of a way of calling the LaunchAction 
directly with an parameters.  Perhaps you can make a special Launch 
Action called CustomLaunchAction which derived from CookieAction and 
provide a cookie called  LaunchJConsoleCookie with getters for various 
parameters needed to configure a JConsole launch.

This is really an extension to the other RFE I sent to you...in this 
case, I could add a dependency between my module Foo and the JMX Support 
Module and I could have Nodes which exposed the CustomLaunchAction.  A 
user upon choosing this action will have a customized launch of the 
JConsole ensue.  For instance, my module may provide a JMX URL, and 
additions to the classpath or in the future a Custom UI blade so that 
the JConsole starts with a custom view.

If an ObjectName could be provided maybe the JConsole could be 
automatically "opened" to a specific MBean."