huw 2002/10/19 12:00:24
Modified: src/xdocs/mx mxinfo.xml
Log:
Specified the mxinfo file should have the same name as the class. Minor rewording.
Revision Changes Path
1.4 +12 -7 jakarta-avalon-phoenix/src/xdocs/mx/mxinfo.xml
Index: mxinfo.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/mx/mxinfo.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- mxinfo.xml 16 Sep 2002 05:40:20 -0000 1.3
+++ mxinfo.xml 19 Oct 2002 19:00:23 -0000 1.4
@@ -13,15 +13,20 @@
to help guide the user.
</p>
<p>
- An mxinfo file is created at design time, either automatically using
xdoclet tags (<a href="xdoctags.html">described here</a>)
- or by hand. At startup the mxinfo file is parsed, and in conjuntion with
class introspection
- is used to define the in-memory metadata for the management of the target
object.
+ An mxinfo file is created at design time. It can be generated
+ automatically using xdoclet tags (<a href="xdoctags.html">described
here</a>)
+ or by hand.
</p>
<p>
- A target object is not restricted to having a single mxinfo file, although
the specifics of how that
- works is dependant on the management component. Similarly it is expected
that
- at runtime the mxinfo file will be located in the classpath of the Target
class, in the same
- package as that class, but this is also under the control of the Container.
Finally, its worth
+ At runtime it is expected that the mxinfo file will be have the same name
+ as the class it describes (e.g. FtpServer.class would be described by an
+ FtpServer.mxinfo file), and be located in the same package as that class.
+ At startup the mxinfo file is parsed and, in conjuntion with class
introspection,
+ is used to define the in-memory metadata for management of the target
object.
+ </p>
+ <p>
+ Note that a target object is not restricted to having a single mxinfo file,
although the specifics of how that
+ works is dependant on the management component. Finally, its worth
pointing out that an mxinfo file generated from interface can be applied to
any class that implements the interface.
</p>
--
To unsubscribe, e-mail: <mailto:avalon-cvs-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@;jakarta.apache.org>
