aboutsummaryrefslogtreecommitdiff
path: root/devel/apache-commons-modeler/pkg-descr
diff options
context:
space:
mode:
Diffstat (limited to 'devel/apache-commons-modeler/pkg-descr')
-rw-r--r--devel/apache-commons-modeler/pkg-descr18
1 files changed, 0 insertions, 18 deletions
diff --git a/devel/apache-commons-modeler/pkg-descr b/devel/apache-commons-modeler/pkg-descr
deleted file mode 100644
index 0487fdbd191b..000000000000
--- a/devel/apache-commons-modeler/pkg-descr
+++ /dev/null
@@ -1,18 +0,0 @@
-java Management Extensions (JMX) is an API that facilitates building management
-applications that can configure, and perform operations on, a server applica
--tion. In general, each manageable component of the server application is re
--presented by a Management Bean (or MBean, for short). JMX defines three types
-of MBeans, of which Model MBeans are the most flexible. Model MBeans provide a
-way to define MBeans for many different components, without having to write a
-specific MBean implementation class for each one.
-
-However, this power comes at a price. It is necessary to set up a substantial
-amount of metadata about each MBean, including the attributes it should expose
-(similar to JavaBeans properties), the operations it should make available (si
--milar to calling methods of a Java object via reflection), and other related
-information. The Modeler component is designed to make this process fairly pain
--less -- the required metadata is configured from an XML description of each
-Model MBean to be supported. In addition, Modeler provides a factory mechanism
-to create the actual Model MBean instances themselves.
-
-WWW: https://commons.apache.org/dormant/commons-modeler/