For some reason, this message did not reach earlier...Yes, in that that's what I'm doing.
On Tuesday 03 February 2004 18:37, Jon Elson-Green wrote:
My understanding of the lifecycle and automatic dependency
resolving clearly needs work, without posting a bunch of sources
could someone suggest where I have gone wrong.
The "Selector" semantics is not supported in Merlin, due to certain vaguenesses surrounding the concept of "hint".
So, Merlin require the Type to the same as the looked up type.
If you depend on a Selector semantic, it is adviced that the client component should be aware the existence of such Selector, and look the Selector up instead and then request the component from the Selector.
Makes sense?
No in that I can't seem to satisfy the selected components required services.
I'm trying to avoid listing the subcomponents dependencies in the class or .xinfo file as that makes it less useful.
The subcomponents are created based on the selector's configuration...if I dont configure a component that needs a datasourceselector, then I don't want a datasourceselector as a dependency of my selector.
Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
