Andreas Frei wrote:
Do you mean by facility orthogonal structures which could be implemented
as aspects?
I hate answering questions like that!
What I mean is that we have a set of licecycle stages - such as logger assignment, configuration, parameterization, servicing, etc. Each of these represent a potentially plugable handler. Perhaps a configuration handler is using Eve as a ldap back end config store - or maybe you want full blown xml handling. That decision should be parameterizable.
What do you mean by plugable lifecycle stages, I am aware of the different component interfaces, but how, when, from where would such a new lifecycle be loaded and activated?
Keep in mind that I'm thinking about lifecycle stage handlers - this is where the new avalon-repsository stuff can be used - to dynamically load a solution on demand. If you take a look at the following code;
http://cvs.apache.org/viewcvs.cgi/avalon/merlin/kernel/plugin/src/java/org/apache/avalon/merlin/tools/MerlinBean.java
Work you way down to the doExecute() method and what you see is the code need to load up a new facilities - in this example its the entire merlin system - but it could equally be a logging subsystem, a configuration handler, whatever you want.
Cheers, Steve.
cheers, Andreas
The recent work on the seperation of the repository facility from thestuff
internals of merlin opens up a bunch of possibilities for scaling down
merlin. For example - the current merlin runtime needs a bunch of
to handle things like XML configurations are so forth - however - muchrather
of this could be parameterized - so for example one could declare a
facility to handle configuration, maybe another facility for logging,
and another for assumbly. Merlin could then bring these in
dynamically. In such a scenario the core merlin system would be
avalon-repository,small - but we are not there yet. There is still a lot to do in both kernel facility management and plugable lifecycle stage handlers.
If I was doing this from scratch - I would start with
avalon-util, avalon-meta as the basic platform and maybe leverage avalon-composition but focussed on serialized descriptors (i.e. no runtime xml).
Cheers, Steve.
Regards, Andreas--
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
