It works perfectly!
Ok, I went through the tutorial. Pretty simple and understandable. Some points are not clear. I.e. has the entry-key attribute [<entry key="cruncher">] given in the block.xml to be the same as in the javadoc tag [EMAIL PROTECTED] key="cruncher" type="tutorial.NumberCruncher"]?
Yes.
The @avalon.entry tag results in the generation of an entry
element in the xinfo. This is turn is read in by the container as an
instance of Type. A type instance exposes a ContextDescriptor which contains a set of EntryDescriptor instances keyed by the entry key value.
When you declare entry parameters in a block you identify the entry using the same key. This information is used to construct an EntryModel which is used by the container to handle the actual context value resolution.
The component deployment descriptor has now its dependency to the implementation used for the cuncher. Is there a way to override this context like in the configuration tutorial by mean of a target in a config.xml?
Not at the moment.
Stephen.
Thanks, Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | 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]
