I started reading the docs about the meta package, the new entries
on the wiki etc. and the more I read the more I get confused (might be my problem, I don't know).
The way I learned about components uses three terms: component, service and implementation. So a component is separated into one (or more) services and the implementation. When assembling my application, I define which implementation I want to use for what service.
Reading now the meta tags, I see that an *implementation* has the avalon.service meta tags that define the services. Good. But what exactly does the avalon.component tag mean?
And more irritating for me: all the meta info is assembled to a "type" and this is where I'm totally lost.
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).
Cheers, Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
