Metro's future Part 2
vinod.p at gmail.com
Fri Mar 4 01:10:21 EST 2005
Nice to see these changes...
On Thu, 3 Mar 2005 23:11:04 +0800, Niclas Hedhman <niclas at hedhman.org> wrote:
-- snip --
> Furthermore, it will be possible to declare a management class of the
> component implementation class (org.hedhman.Niclas in the example above),
> which manages the component model and the instances coming out of that model.
> I.e. it will be possible to make management extensions per component, which
> is neatly integrated with the Metro management principles. Possibly, the
> component management class is provided (or can find) the controllers defined
> in the system for the meta type of the component it manages. Details here are
> still not totally ironed out, but it is apparent that a
> @metro.management class="com.def.Abc"
> of some form will be introduced, and that will be written into the .xinfo
does this mean that each component will have exactly one management
class? What would be the responsibilities of this management class?
And does this also mean that any other component that wants to use the
'niclas' component and "control" it has to go via the management
More information about the dev-dpml