You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by mc...@apache.org on 2002/07/08 01:14:03 UTC
cvs commit: jakarta-avalon-excalibur/assembly/src/java/org/apache/excalibur/merlin/registry package.html
mcconnell 2002/07/07 16:14:03
Modified: assembly/src/java/org/apache/excalibur/merlin/registry
package.html
Log:
javadoc updates
Revision Changes Path
1.6 +1 -1 jakarta-avalon-excalibur/assembly/src/java/org/apache/excalibur/merlin/registry/package.html
Index: package.html
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/assembly/src/java/org/apache/excalibur/merlin/registry/package.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- package.html 7 Jul 2002 04:28:31 -0000 1.5
+++ package.html 7 Jul 2002 23:14:02 -0000 1.6
@@ -18,7 +18,7 @@
</ul>
<h3>Object Model</h3>
-<p>The registry object model provides a simplified view of the <code>containerkit</code> framework. The principal entry point is the {@link org.apache.excalibur.merlin.registry.Registry} and the associated default implementation {@link org.apache.excalibur.merlin.registry.DefaultRegistry}. The registry acts as a component type repository. Component types are exposed as instances of the {@link org.apache.excalibur.meta.info.Type} interface. Each component type represents a concrete component implementation class. For each component type, the container associates at least one instantiation {@link org.apache.excalibur.meta.data.Profile}. A profile is either a default profile generated by the registry based on meta-information derived from the type, or, an explicit profile declared by the component assembler via the registry configuration. Multiple profiles for a particular component type can coexist in the same registry.
+<p>The primary service is a type {@link org.apache.excalibur.merlin.registry.Registry}. The registry acts as a component {@link org.apache.excalibur.meta.info.Type} repository and {@link org.apache.excalibur.meta.data.Profile} manager. Each component type represents a concrete component implementation class. For each component type, the container associates at least one instantiation {@link org.apache.excalibur.meta.data.Profile}. A profile is either a default profile generated by the registry based on meta-information derived from the type, or, an explicit profile declared by the component assembler via the registry configuration. Multiple profiles for a particular component type can coexist in the same registry.
<h3>Package Structure (UML)</h3>
<p><img src=doc-files/registry.gif border=0></p>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>