WcfFacility: controlling service lifestyle

Question

Registration example:

        container.Register(Component.For<IFooService>().ImplementedBy<FooService>().AsWcfService<IFooService>(new DefaultServiceModel().Hosted()).LifestyleTransient());

.svc:

<%@ServiceHost language="C#" Debug="true" Service="Service.FooService" 
Factory="Castle.Facilities.WcfIntegration.DefaultServiceHostFactory, Castle.Facilities.WcfIntegration" %>

The WCF is hosted in IIS and when I hit the endpoint using WcfStorm the ctor is not called upon every request. If I regenerate the client-side proxy the ctor is called once again. How can the service lifecycle be coupled to the client side proxy?

In general, the service lifecycle has nothing to do with the client proxy. This is not Remoting. — John Saunders, Jun 17 '14 at 14:25
Of course I understand that, but this does not clarify the behaviour I am observing — Marius, Jun 17 '14 at 15:25

score 0 · Accepted Answer · answered Jun 18 '14 at 06:12

Transient will behave like Transient should, meaning that Castle.Windsor will create a new service instance upon request. The confusion came from the fact that this did not happen every time the service was hit. The reason for this is that the WCF stack has its own idea of service lifetime, defined by the "InstanceContextMode" which default to "PerSession". If I changed the InstanceContextMode to "PerCall", Castle will comission/decomission the services as (I) expected.

[ServiceBehavior(InstanceContextMode = InstanceContextMode.PerCall)]
public class FooService : IFooService { .. }

WcfFacility: controlling service lifestyle

1 Answers1