Stephen McConnell wrote: > > From the front page: > > The Avalon Meta Model defines the functional structure > of component types and services. A Type definition > contains information about deployment and runtime > dependencies together with information about the > services that a component type can provide. > > The following page describes the XML schema used to define a > Type instance - > http://avalon.apache.org/meta/meta/info/type/index.html > This is paralleled in the API documentation for the immutable > Type class (org.apache.avalon.meta.info.Type). Keep in mind > that the Type is simply an immutable class that exposes all > of the descriptive features of a component (that's it). > Ok. So by defining a type I don't "create" a component, which means if I only define a type, I can't lookup up something?
Now, we could argue about the correct terms for months but the term "type" is imho misleading here. If a type exposes all features of a component why is it called a type and not component? Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
