Leo Sutic wrote:
Primarily a meta-meta model.Stephen, what does clazz provide that we want?
That means is that someone writting a tool for [clazz] based meta model does not need to be concerned with anything specific to Avalon. They will write tools in terms of clazz properties, clazz operatioins, attributes etc - and never need to have any specific knowlege about "our domain". For example, tools such as descriptor and document generators, navigators, conversion tools, ... that are written for clazz will work with our model (bacause the model will use the same meta-meta model).
Secondly, the package provides a nice structure for integration of meta information at a clazzloader level. The object model provides support for locating a clazz, instance creation from the clazz and so on. With this seperation between Java class and the [clazz] notion of a class, my impression is that we will be able to achieve a lot of behind the scenes simplification of "component and service management".
Cheers, Steve.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- 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]>
