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 affort when Craig updates facility code.
Facility registres lazy loader:
Component.For<ILazyComponentLoader>().ImplementedBy<WcfClientComponentLoader>()
all I need is to get rid of thid loader. Is there any way to unregister
component from container?
On Monday, April 1, 2013 4:50:19 AM UTC+4, Krzysztof Koźmic wrote:
>
> 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
>
> [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<WcfFacility>();
> var p=container.Resolve<ISecurityProvider>();
>
> 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 [email protected].
To post to this group, send email to [email protected].
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.
