Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.apache.commons.modeler.ant.* (7)org.apache.commons.modeler.demo.* (6)
org.apache.commons.modeler.mbeans.* (2)org.apache.commons.modeler.modules.* (8)
org.apache.commons.modeler.util.* (2)

org.apache.commons.modeler: Javadoc index of package org.apache.commons.modeler.


Package Samples:

org.apache.commons.modeler.ant: The Modeler component of the Jakarta Commons subproject offers convenient support for configuring and instantiating Model MBeans (management beans), as described in the JMX Specification.  
org.apache.commons.modeler.mbeans
org.apache.commons.modeler.modules
org.apache.commons.modeler.util
org.apache.commons.modeler.demo

Classes:

BaseModelMBean: Basic implementation of the ModelMBean interface, which supports the minimal requirements of the interface contract. This can be used directly to wrap an existing java bean, or inside an mlet or anywhere an MBean would be used. The String parameter passed to the constructor will be used to construct an instance of the real object that we wrap. Limitations: Only managed resources of type objectReference are supportd. Caching of attribute values and operation results is not supported. All calls to invoke() are immediately executed. Logging (under control of descriptors) is not supported. Persistence ...
JndiJmx: Link between JNDI and JMX. JNDI can be used for persistence ( it is an API for storing hierarchical data and a perfect fit for that ), as well as an alternate view of the MBean registry. If this component is enabled, all MBeans will be registered in JNDI, and all attributes that are set via JMX can be stored in a DirContext. This acts as a "recorder" for creation of mbeans and attribute changes done via JMX. XXX How can we control ( filter ) which mbeans will be registere ? Or attributes ? XXX How can we get the beans and attributes loaded before jndijmx ? The intended use: - do whatever you want ...
Registry: Registry for modeler MBeans. This is the main entry point into modeler. It provides methods to create and manipulate model mbeans and simplify their use. Starting with version 1.1, this is no longer a singleton and the static methods are strongly deprecated. In a container environment we can expect different applications to use different registries. This class is itself an mbean. IMPORTANT: public methods not marked with @since x.x are experimental or internal. Should not be used.
SimpleRemoteConnector: Based on jk2 proxy. Proxy using a very simple HTTP based protocol. For efficiency, it'll get bulk results and cache them - you can force an update by calling the refreshAttributes and refreshMetadata operations on this mbean. TODO: implement the user/pass auth ( right now you must use IP based security ) TODO: eventually support https TODO: support for metadata ( mbean-descriptors ) for description and type conversions TODO: filter out trivial components ( mutexes, etc )
FixedNotificationFilter: Special NotificationFilter that allows modeler to optimize its notifications. This class is immutable - after you construct it it'll filter based on a fixed set of notification names. The JMX specification requires the filters to be called before the notifications are sent. We can call this filter well in advance, when the listener is added. Based on the result we can maintain separate channels for each notification - and reduce the overhead.
MbeansDescriptorsDynamicMBeanSource: Extract metadata from a dynamic mbean. Used to wrap a dynamic mbean in order to implement persistence. This is really an ugly asspect of the JMX spec - we need to convery from normal metainfo to model metainfo. The info is the same, but they use a different class. Just like the DOM spec - where all implementations get an order of unneeded complexity from the various types.
RegistryMBean: Interface for modeler MBeans. This is the main entry point into modeler. It provides methods to create and manipulate model mbeans and simplify their use. Starting with version 1.1, this is no longer a singleton and the static methods are strongly deprecated. In a container environment we can expect different applications to use different registries.
MbeansSource: This will create mbeans based on a config file. The format is an extended version of MLET. Classloading. We don't support any explicit classloader tag. A ClassLoader is just an mbean ( it can be the standard MLetMBean or a custom one ). XXX add a special attribute to reference the loader mbean, XXX figure out how to deal with private loaders
BaseAttributeFilter: Implementation of NotificationFilter for attribute change notifications. This class is used by BaseModelMBean to construct attribute change notification event filters when a filter is not supplied by the application.
FeatureInfo: Convenience base class for AttributeInfo , ConstructorInfo , and OperationInfo classes that will be used to collect configuration information for the ModelMBean beans exposed for management.
MLETTask: Load an MBean. The syntax is similar with the , with few ant-specific extensions. A separate classloader can be used, the mechanism is similar with what taskdef is using. Note that mlet will use the arguments in the constructor.
BaseNotificationBroadcaster: Implementation of NotificationBroadcaster for attribute change notifications. This class is used by BaseModelMBean to handle notifications of attribute change events to interested listeners.
Demo: Demonstration program for the Modeller package. Instantiates a set of simple managed objects, and a set of corresponding MBeans, then manipulates the objects through the MBean interfaces.
MbeansSourceMBean: This mbean will load an extended mlet file ( similar in syntax with jboss ). It'll keep track of all attribute changes and update the file when attributes change.
Main: Small main that loads mbeans. Requires: commons-logging-api.jar, jaxp ( including DOM ), jmx Arguments: -file FILE Will load mbeans from the file
Connector: Sample managed object for the Modeler Demonstration Application, based on the Catalina architecture of Tomcat 4.
Container: Sample managed object for the Modeler Demonstration Application, based on the Catalina architecture of Tomcat 4.
Engine: Sample managed object for the Modeler Demonstration Application, based on the Catalina architecture of Tomcat 4.
Server: Sample managed object for the Modeler Demonstration Application, based on the Catalina architecture of Tomcat 4.
Service: Sample managed object for the Modeler Demonstration Application, based on the Catalina architecture of Tomcat 4.
FieldInfo: Simple JavaBean representing the contents of a <field> element in an MBeans descriptor file.
BaseNotification: Base JMX Notification. Supports in int code and notes - for faster access and dispatching.
NotificationInfo: Internal configuration information for a Notification descriptor.
ConstructorInfo: Internal configuration information for a Constructor descriptor.
AttributeInfo: Internal configuration information for an Attribute descriptor.

Home | Contact Us | Privacy Policy | Terms of Service