hi niclas, thanks for your detailed answer. because i'm very new to avalon i had to think a while whether i understood it.
do you basically suggest to enhance my signalling classes with full support for avalon lifecycle control? 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)? i'll have to revisit the respective signatures for wehether i'm able to feed them manually... 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). /eike "Niclas Hedhman" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > I think you first need to ask yourself; > > "What part of Avalon/Merlin will bring me the benefits in my system?" > > You mention config, logging, jmx, so let's start with that. > > Easiest to write off is JMX. It is a facility in Merlin, and if you don't use > Merlin it is fairly difficult to instantiate it on its own. > > Logging; Let the components be LogEnabled (or extend AbstractLogEnabled). The > client then directly instantiate a Logger, either your own or one of the > simple ones, like ConsoleLogger. > > Configuration; Basically the same thing here. Merlin handles the server side, > and on the client side, you instantiate a DefaultConfigurationBuilder and > build a Configuration from whereever you stick it. > > > This expects that you can manage the 'instantiation' on the client without > problem, and don't need 'assembly' support there. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
