"Stephen McConnell" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > Eike Stepper wrote: > > > from your answer i'm not totally sure who made the mistake. > > I wrote the code that is causing the problem but I think we should hold > Niclas responsible .. after all - he's asleep and he's not going to > complain anytime in the next 8 hours. > > ;-)
it was not my intention to blame anyone but me ;-) > > the concepts of > > nesting containers are a bit unclear to me. > > If a container declares that it exports services then in effect the > container is functioning as a logical component. This 'feature' is > central to the ability to build solutions via composition (which is an > area that directly linked with the Merlin Discovery strategy - i.e. > server side creation of composite solutions on demand - but I'm drifting > off topic here). > > > up to now i've found them to be the > > only means to provide multiple service-to-component mappings and i use them > > only for that purpose. > > Providing multiple service to a component is a basic capability - my > guess is that your dealing with the issue of service visibility. In > your case you client component is kind of isolated. Keep in mind that > the service logically visible to the client are those service exported > by components (or containers at the same or higher level than the client). > > container:[/]) > children: > container:[/app]) > children: > container:[/app/net4j]) > --> [/app/Client1] > > # > # snip-non-visible-children > # > | only visible > component:[/app/Client1](0) <-------| component at this > <-- [/app/net4j] | level is the > | /app/net4j > | composite > startup: > 1: [/app/net4j] > 2: [/app/Client1] > shutdown: > 1: [/app/Client1] > 2: [/app/net4j] > startup: > 1: [/app] > shutdown: > 1: [/app] that was really useful for my understanding of service resolution in general. you should consider to integrate such an example into the docs. i have the impression that you are so familar with thinking in services, components and containers that you can't imagine anymore how complicated all this might seem for more old-fashioned designers like me ;-)))) in fact i dare all this only because i have the feeling that it improves the design and the manageability of many applications tremendously. now it starts to make fun. nevertheless i keep finding me in the situation that i think to understand the mechanisms because my app is running only to recognize that i was totally blind. one reason for this might be (i repeat myself ;-) that the docs are spread over many projects. for a merlin user there is no central and complete place for information. many times the only way to proceed was to discover the sources of the spare open source projects that build on merlin. and of course your prompt and detailed replies - thanks... /eike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
