There are startable components that are instanciated once all dependencies 
can be resolved. Logic is based on it, implicit registration triggers 
initialization before it can be finished.

On Monday, April 1, 2013 8:15:26 PM UTC+4, Craig Neuwirt wrote:
>
> 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 
> <konstant...@gmail.com<javascript:>
> > wrote:
>
>> 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.com>wrote:
>>>
>>>> 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 balancing proxy 
>>>> to 
>>>> all components dependent on service contract), but after I updated to 
>>>> latest  wcf facility version that introduces implicit registration feature 
>>>> all this stuff stopped working since facility injects non functional proxy 
>>>> (there is no configuration in app.config)
>>>>
>>>>
>>>> The following change of WcfFacility will solve all my problems:
>>>>
>>>>     public bool DoNotRegisterComponentsImplici**tly{get;set;}
>>>>
>>>>     protected override void Init()
>>>>     {
>>>>            ...
>>>>            if(!**DoNotRegisterComponentsImplici**tly)
>>>>                  Component.For<**ILazyComponentLoader>().**
>>>> ImplementedBy<**WcfClientComponentLoader>()
>>>>     }
>>>>
>>>>
>>>> Usage:
>>>> container.AddFacility<**WcfFacility>(f=>f.**
>>>> DoNotRegisterComponentsImplici**tly=true);
>>>>
>>>>
>>>>
>>>> On Monday, April 1, 2013 3:46:12 PM UTC+4, Craig Neuwirt wrote:
>>>>
>>>>> So what would you want to happen when you call container.Resolve<**
>>>>> ISecurityPro**vider>()?  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 <konstant...@gmail.com>wrote:
>>>>>
>>>>>> lets say I have some service contract 
>>>>>>
>>>>>> [ServiceContract]
>>>>>>     public interface ISecurityProvider
>>>>>>     {
>>>>>>          [OperationContract]
>>>>>>         void DoSomething();
>>>>>> }
>>>>>>
>>>>>>
>>>>>> following code throws exception: 
>>>>>> Castle.MicroKernel.****Facilities.FacilityException 
>>>>>> : The client model requires an endpoint.
>>>>>>
>>>>>>             WindsorContainer container=new WindsorContainer();
>>>>>>             container.AddFacility<**WcfFacil**ity>();
>>>>>>             var p=container.Resolve<**ISecurityP**rovider>();
>>>>>>
>>>>>> It is convinient when WCF is configured in app.config. In my case app 
>>>>>> listens topic in messageing to get the address where and how to access 
>>>>>> service. So when container is initially configured service contracts 
>>>>>> should 
>>>>>> not be resolvable. 
>>>>>>  
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Castle Project Users" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to castle-project-users+**unsubscri**
>>>>>> b...@googlegroups.com.
>>>>>> To post to this group, send email to castle-pro...@**googlegroups.com
>>>>>> **.
>>>>>>
>>>>>> Visit this group at http://groups.google.com/**group**
>>>>>> /castle-project-users?hl=**en<http://groups.google.com/group/castle-project-users?hl=en>
>>>>>> .
>>>>>> For more options, visit 
>>>>>> https://groups.google.com/**grou**ps/opt_out<https://groups.google.com/groups/opt_out>
>>>>>> .
>>>>>>  
>>>>>>  
>>>>>>
>>>>>
>>>>>  -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Castle Project Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to castle-project-users+**unsubscr...@googlegroups.com.
>>>> To post to this group, send email to castle-pro...@**googlegroups.com.
>>>> Visit this group at http://groups.google.com/**
>>>> group/castle-project-users?hl=**en<http://groups.google.com/group/castle-project-users?hl=en>
>>>> .
>>>> For more options, visit 
>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>> .
>>>>  
>>>>  
>>>>
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Castle Project Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to castle-project-users+unsubscr...@googlegroups.com <javascript:>.
>> To post to this group, send email to 
>> castle-pro...@googlegroups.com<javascript:>
>> .
>> Visit this group at 
>> http://groups.google.com/group/castle-project-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to castle-project-users+unsubscr...@googlegroups.com.
To post to this group, send email to castle-project-users@googlegroups.com.
Visit this group at http://groups.google.com/group/castle-project-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to