On Mon, 2003-07-21 at 16:00, Berin Loritsch wrote:
> The ones that are close to the current AMTAGS proposal are:
>
> @avalon.component, @avalon.service, and @avalon.dependency
So what are the issues of adopting these three tags as defined by the
meta package into AMTAGS?
> Now, for the lifecycle extensions tags (i.e. @avalon.extension, @avalon.stage)
> I propose that we move them to a functional namespace: @lifecycle.extension and
> @lifecycle.stage). I still get confused over which references what, so I need
> a little information on that. Does ".extension" reference the interface that
> is the lifecycle extension? If so, that would mean that ".stage" would
> reference the Creator/Accessor that does the actual logic for extending the
> component's lifecycle.
Stage = service which uses a lifecycle extension
Extension = service which can provide support for a lifecycle extension
I get them mixed up too.
Merlin also has support for what are currently dubbed
"DeploymentStageExtensions" which are similar to Lifecycle Creator
Extensions, only these extensions have access to the Appliance.
Also, Stephen recently added support for extension handlers to be
identified by strings (think urn's) instead of class names. These two
modifications open up a number of possibilities and I'd like to see
support for it eventually make it's way into Fortress and Phoenix.
> Lastly we have a generic @avalon.attribute tag that is nice and flexible.
> However, it is unclear to me from the code where it is recognized. It appears
> to only be recognizable from the main class JavaDocs from the ANT tag code.
> According to the model code, attributes would be applicable to the type, the
> service, and dependencies. It is unclear to me how we scope the attributes
> to the specified dependency or service (if the service is specified with the
> component implementation).
Yes. I had trouble with this as well. For example, the following
should be valid in a merlin .xinfo file:
<stages>
<stage type="org.apache.avalon.plyground.Demonstratable:1.0.0">
<attributes>
<attribute name="description" value="an example"/>
<attribute name="color" value="red"/>
<attribute name="priority" value="normal"/>
</attributes>
</stage>
</stages>
But I have no idea how to specify this in doclet tags. In fact, I'm not sure if the
current code supports it.
--
jaaron <http://jadetower.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
