Paul Hammant wrote:
Is it really necesary for us to come up with a single set of tags now is it? Let it slideuntil
JSR-111 comes out.That will be a while (we both know that).
:-)
What we want for Avalon is to provide a set of attributes that we build
upon so that the user has a smooth migration path.
To be honest doclet tags are not that important. The meta-data form is.
The doclet tags are orthoginal to the meta-data. What the doclet tags enable is a consitent apprach to the declaration of features of the component type in a manner that is independent of the underlying meta model. For example, Berin has written an ant task that allows him to generate information that is specific to Fortress. Within a few days I'll publish something that will take the same tags and generate a different meta model - in fact I'll probably provide support for generating the native Merlin meta model and/or the legacy Phoenix model. Image what happens when Berin and I start thinking about converging. We have in front of us the seperation of the specification from the underlyiung model + the abilioty to generate the model for every container in Avalon. Not bad if think about it. Even better when you consider that we have isolated out the meta model as far as the user in concerned.
Principally what is in a in an XML file adjacent to the class file, in the jar. We'll always allow people to build avalon comps without using doclet tags if they want right? So why do this design thing on doclet tags?
Because it makes things easier - reduces the adoption barrier - makes things more reliable.
Besides. We will change things twice from now on if we do rescope JSR-111.
That's a question folowing a JSR-111 release. Switching in a different meta model is achivable.
My simple assertion is that doclet tags are not hindering adoption of Avalon presently.
Not sure - I've received at least three request for exactly this relative to the Merlin Meta Model. As I mentioned above I should have something to automate Merlin meta info generation in a few days. This should include an ant task and a maven meta generator plugin. What this means is that the developer focus can shift from crafting XMML .xinfo files to expressing this in @avalon. From there we have a fantastic advance - Fortress, Merlin and Phoenix sharing a small, minimal but common set of semantics.
Wow - yes - is this right or what!
Cheer, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
