donaldp 2002/09/06 15:42:12
Modified: src/xdocs Tag: RELEASE_402-branch guide-mx-mxinfo.xml
Log:
Line length fixed.
Revision Changes Path
No revision
No revision
1.1.2.1 +3 -2 jakarta-avalon-phoenix/src/xdocs/guide-mx-mxinfo.xml
Index: guide-mx-mxinfo.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-mx-mxinfo.xml,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- guide-mx-mxinfo.xml 20 Aug 2002 04:50:46 -0000 1.1
+++ guide-mx-mxinfo.xml 6 Sep 2002 22:42:11 -0000 1.1.2.1
@@ -34,13 +34,14 @@
A target object is not restricted to having a single mxinfo file,
although the specifics of how that
works is dependant on the container (described [TODO] here).
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 pointing out that an mxinfo file generated from
interface can be applied to
+ package as that class, but this is also under the control of the
Container. Finally, its worth
+ pointing out that an mxinfo file generated from interface can be
applied to
any class that implements the interface.
</p>
</section>
<section name="Example" >
<p>
- Since mxinfo files are somewhat confusing in the abstractm, but
straight forward in practice,
+ Since mxinfo files are somewhat confusing in the abstract, but
straight forward in practice,
the rest of this section describes an imaginary, yet somewhat
plausible, mxinfo file.
</p>
<source>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
