Hi Peter,
it's the other way around - assume that a component is instantiated as a child but implements ServiceManager, Would Excalibur ever invoke lookup()?!
The usage szenario would be : you find a few funky Fulcrum services but they depend on a Merlin Avalon contract regarding the Context. If I understand it correctly you can't use the components directly since the blow up during contextialize() trying to access "urn:avalon:home" and "urn:avalon:temp". In this case you can instantiate YAAFI as Excalibur component whereas YAAFI takes care of loading the Fulcrum components. But the YAAFI instance would be a child component and the available service would be never found during the cascading lookup going up the parent hierarchy. Do I miss something here)
We have the same requirement for Turbine - if the Turbine service framework does not find a service it should ask all its children implementing ServiceManager. In this case it is not a big deal since this is the only sensible solution to provide container-transparent access to components. But in Excalibur land it has a rather akward semantic.
Cheers,
Siegfried Goeschl
peter royal wrote:
On Feb 15, 2005, at 12:48 PM, Siegfried Goeschl wrote:
The only remaining issue is that I don't know if there is cascading lookup() implemented in Excalibur. E.g. if a component implements a ServiceManager interface you could delegate the search if you own container hasn't found anything and a proper sematic ... any comments from the Excalibur community?!
Not sure what you mean.. The DefaultServiceManager implementation has a cascading behavior, it will search in a parent SM if a component is not contained within itself..
-pete
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
