Andrei Ivanov wrote:
>2. what has to be done long ago: is GETTING RIDE OF xinfo files (xdoclet
>rules!!!)
>
You may want to hold off on this for a little while. Currently over in
Avalon land there is work going on concerning a standard "meta model"
that will be described using an xinfo resource that has the potential to
enable component deployment across a number of different containers.
Currently James uses Phoenix as its container and describes component
meta-info in a blockinfo descriptor. It is expected that Phoenix will
be enhanced to support a more standard meta info DTD in the near future.
In the meantime there is work on-going with two other containers -
Fortress and Merlin. The authors of these containers are working
together to ensure the establishment of a meta-model that completely
addresses not only the defintions of component services and depenedecies
along the lines of the blockinfo model, but addition contextn such as
lifecycle extensions, lifestyle management, and so on. When this all
settles down I expect we will see support in Phoenix for the
Fortress/Merlin meta-model and support for blockinfo declarations inside
Merlin.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
