So what would you want to happen when you call container.Resolve<ISecurityProvider>()? 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 <[email protected]>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. > > > -- 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.
