On Saturday 29 May 2004 20:46, Eike Stepper wrote:
> do you basically suggest to enhance my signalling classes with full
> support for avalon lifecycle control?
It is your choice whether you want "full support" or "partial support", and
that is why you need the question; "Where are the benefits to be harvested?"
> that would mean to deploy the
> avalon jars to the client (because of the implemented interfaces),
> run merlin server-side and let the client call the avalon methods
> directly (instead of merlin)?
Yes, on the client, "handle instantiation" was my way of saying, you know how
to create the components (new AbcComponent(), factories and/or through
reflection or whatever ), and in that process have code similar to;
Logger logger = new Console Logger();
if( comp instanceof LogEnabled )
((LogEnabled) com).enableLogging( logger );
boolean ns = false; // Namespace support or not.
DefaultConfigurationBuilder dcb = new DefaultConfigurationBuilder( ns );
if( comp instanceof Configurable )
{
Configuration conf = dcb.buildFromFile( configFile );
// or read from InputSource, InputStream and a few others.
((Configurable) conf).configure( conf );
}
+ the exception handling of course.
Same goes if you want to support any of the other LifeCycle interfaces.
That part of Avalon is fairly straight forward to understand and implement by
yourself outside the robust Merlin platform.
> i've no clue yet what assemblies and facilities are although i saw those
> terms spread over the documentation (which i find quite confusing btw).
Facilities = Components that have access to the Merlin internals. To provide
the JMX (which is a facility (still in development)) support in your client
(for whatever reason), would require you 'home grown' container to replicate
the Merlin internals, which is far too much work, and you would be better off
embedding Merlin into your clients.
Assembly = The process of declaring which components goes into and
application, and how they are 'wired' together. The Assembly information is
used by the Merlin Composition subsystem which creates a model of the
Assembly (a.k.a The Model) of the application, which the Merlin Activation
subsystem will instantiate, configure and in other ways manage during the
runtime phase.
If you could provide a little bit more info about your client side, we might
provide some advice on whether or not an Embedded Merlin is to recommend over
a 'home grown' container surrogate.
Cheers
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
