I'm sorry I didn't follow this thread earlier. > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons > > Joerg Heinicke wrote: > > Niclas Hedhman <niclas <at> hedhman.org> writes: > > > >>No, the issue at hand is that IF the client-component is written against > a > >>"observed behaviour" of a particular container, re-use and > interchangeable > >>compents between containers suffers. > > > > Sorry, but I don't get it. Why is the selector container specific? > > because some containers (ie Phoenix) do not support the mechanism. I'm > not sure whether merlin supports it, and if its mechanism is fully > compatible with the one used in fortress and ecm (which are compatible).
Merlin does NOT support ServiceSelectors. Moreover, Merlin requires that components declare ALL service dependencies. That means unlike ECM/Fortress, you cannot just lookup anything from the ServiceManager. If your component did not declare a dependency on it, then you're out of luck. This is a feature (security) not a bug, though I find it annoying sometimes. > > Ok. So the selection itself is ok, but not the to generic service > selector. but > > then the statement "the usage service selector might be related to bad > design" > > is to universal, isn't it? The biggest problem with ServiceSelectors in Avalon is the wide range of support or lack thereof. So it's better to just roll your own Selector-like object as Leo mentioned. If you have any other specific questions about lookup semantics, let me know. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
