I see.
I've take a look at WcfFacility code, it initializes private fields in
Init, so I have only 2 options:
1. Inherit from WcfFacility and use reflection to init same fields
2. Fork facility code
Boath does not look to be apropriate way - first is dirty, second will
require additional
So what would you want to happen when you call
container.ResolveISecurityProvider()? We could possibly introduce some
kind of DynamicWcfClientModel to defer or delay selection of the
WcfClientModel.
On Sun, Mar 31, 2013 at 3:22 PM, Konstantin konstantin.no...@gmail.comwrote:
lets say I have
I'd like to have no ISecurityProvider component registered unless I
register it explicitly.
I've already implemented deferred registration (component listens for
heartbeats from server, discovers service instances and registers clients
for each discovered instance. Actually it also provides
Aren't you explicitly registering ISecurityProvider in your case?
On Mon, Apr 1, 2013 at 6:56 AM, Konstantin konstantin.no...@gmail.comwrote:
I'd like to have no ISecurityProvider component registered unless I
register it explicitly.
I've already implemented deferred registration (component
I register service only when recieve first heartbeat from it.
On Monday, April 1, 2013 4:48:16 PM UTC+4, Craig Neuwirt wrote:
Aren't you explicitly registering ISecurityProvider in your case?
On Mon, Apr 1, 2013 at 6:56 AM, Konstantin konstant...@gmail.comjavascript:
wrote:
I'd like to
Ok. And can that service be resolved before it is registered? If not,
the WCF component loader should not be triggered
On Mon, Apr 1, 2013 at 10:58 AM, Konstantin konstantin.no...@gmail.comwrote:
I register service only when recieve first heartbeat from it.
On Monday, April 1, 2013
I don't think there's a switch that controls that (Craig may have some input
here)
I think if you want that you might need to override some logic in the facility
--
Krzysztof Kozmic
On Monday, 1 April 2013 at 6:22 AM, Konstantin wrote:
lets say I have some service contract
