-project-users@googlegroups.com
Subject: Re: Last change to register kernel dependencies
I looked at IlazyComponentLoader, but that only kicks in if nothing is
registered...
Well isn't that what you need? It seems to be the case from what you said in
just before resolution, it's dependencies
From: castle-project-users@googlegroups.com on behalf of Krzysztof Kozmic
Sent: Mon 25/04/2011 5:48 p.m.
To: castle-project-users@googlegroups.com
Subject: Re: Last change to register kernel dependencies
I looked at IlazyComponentLoader, but that only kicks in if nothing is
registered...
Well
: Re: Last change to register kernel dependencies
I'm obviously not seeing the whole picture but I get the feeling that an
asynchronous publish/subscribe architecture with message passing might
work better than synchronous RPC via remoting.
Are there any particular reasons why you want to do
I require a way to get a last chance to register a components dependencies
before resolution occurs.
I am writing a custom facility, but I need to first register a component which
has missing dependencies, then just before resolution, it's dependencies are
registered.
What extension points
I looked at IlazyComponentLoader, but that only kicks in if nothing is
registered...
Well isn't that what you need? It seems to be the case from what you said in just
before resolution, it's dependencies are registered
Can you elaborate a bit more why you need that behaviour and what
