On Tuesday 01 June 2004 18:31, Eike Stepper wrote: > hi, > > i started a new thread because the other (server code shared with clients) > became quite long. as i already told, i've been able to start a merlin > DefaultKernel which then loads and starts some services (components?). up > to now i have not found a way to access those services from outside of the > kernel/container. although i think there should be a clean (merlin) > solution, i would like to know what you think about the following > work-around: > > i could create a registry map before starting the kernel and pass a handle > via the context to the components. on start/stop they could > register/deregister with that registry. so that the outside world has > access to the running components in the container. > > does that sound too awful and is there a more merlin way?
So, you are talking about systems outside the components managed by Merlin?? If so, the 'proper' way is to create a "facility", which is a component that is declaring that it wants the composition model in its context. Once the facility gets the Model, it registers itself as a listener to model changes, and can expose the available components to other parties, over whatever medium is most convenenient/necessary. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
