1
0
mirror of https://git.FreeBSD.org/ports.git synced 2025-02-04 11:23:46 +00:00

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.

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.

Homepage:	http://jakarta.apache.org/commons/modeler/
Submitted by:	Nemo LIU <nemoliu at gmail dot com>
PR:		ports/109074
This commit is contained in:
Xin LI 2007-02-13 07:06:52 +00:00
parent a54ba76b59
commit 8818312988
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=185077
4 changed files with 67 additions and 0 deletions

View File

@ -462,6 +462,7 @@
SUBDIR += jakarta-commons-configuration
SUBDIR += jakarta-commons-io
SUBDIR += jakarta-commons-jxpath
SUBDIR += jakarta-commons-modeler
SUBDIR += jakelib2
SUBDIR += jam
SUBDIR += java-util-concurrent

View File

@ -0,0 +1,45 @@
# ports collection makefile for: Jakarta Commons Modeler
# Date created: February 08, 2007
# Whom: Nemo Liu <nemoliu@gmail.com>
#
# $FreeBSD$
#
PORTNAME= commons-modeler
PORTVERSION= 2.0
CATEGORIES= devel java
MASTER_SITES= ${MASTER_SITE_APACHE_JAKARTA}
MASTER_SITE_SUBDIR= ${PORTNAME:S,-,/,}/binaries
PKGNAMEPREFIX= jakarta-
MAINTAINER= nemoliu@gmail.com
COMMENT= Mechanisms to create Model MBeans compatible with JMX specification
USE_JAVA= yes
JAVA_VERSION= 1.2+
NO_BUILD= yes
.include <bsd.port.pre.mk>
.if !defined(NOPORTDOCS)
PORTDOCS= *
.endif
PLIST_FILES= %%JAVAJARDIR%%/${PORTNAME}.jar
do-install:
@${ECHO_MSG} -n ">> Installing JAR as ${JAVAJARDIR}/${PORTNAME}.jar..."
@${INSTALL_DATA} ${WRKSRC}/${PORTNAME}-${PORTVERSION}.jar ${JAVAJARDIR}/${PORTNAME}.jar
@${ECHO_MSG} " [ DONE ]"
.if !defined(NOPORTDOCS)
@${ECHO_MSG} -n ">> Installing documentation in ${DOCSDIR}/..."
@cd ${WRKSRC}/docs \
&& ${FIND} . -type d -exec ${MKDIR} ${DOCSDIR}/docs/{} \; \
&& ${FIND} . -type f -exec ${INSTALL_DATA} {} ${DOCSDIR}/docs/{} \;
@${INSTALL_DATA} ${WRKSRC}/LICENSE.txt ${DOCSDIR}/
@${INSTALL_DATA} ${WRKSRC}/NOTICE.txt ${DOCSDIR}/
@${INSTALL_DATA} ${WRKSRC}/RELEASE-NOTES.txt ${DOCSDIR}/
@${ECHO_MSG} " [ DONE ]"
.endif
.include <bsd.port.post.mk>

View File

@ -0,0 +1,3 @@
MD5 (commons-modeler-2.0.tar.gz) = ba74fdf4aca98f01579eca11acc6d882
SHA256 (commons-modeler-2.0.tar.gz) = 9c2a78fd994f669e720b4b3e9763f4bcac76512d4562217ca2254e494d726d54
SIZE (commons-modeler-2.0.tar.gz) = 476366

View File

@ -0,0 +1,18 @@
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: http://jakarta.apache.org/commons/modeler/