}

> To the best of my knowledge, Autofac doesn't have a feature to do DI into
> endpoint behaviors, so you'd have to resolve the dependency manually. (Nick
> will, I'm sure, jump in here and correct me if I'm wrong.) So in your
> behavior where you need your IUnitOfWork as a constructor parameter, you'd
> instead resolve it directly:

> public UnitOfWorkEndpointBehavior()
> {
>   this.unitOfWork = AutofacHostFactory.Container.Resolve<IUnitOfWork>();

> }

> You can still apply behaviors through XML configuration using Autofac, just
> like normal, but if you want to do it programmatically you can have a
> custom host factory based on AutofacServiceHostFactory and use the
> ConfigurationAction static property

> UnitOfWorkAutofacHostFactory.ConfigurationAction =
>   host =>
>     host.Opening += (sender, args) =>
>       host.Description.Behaviors.Add(new UnitOfWorkEndpointBehavior());

> Then specify the custom UnitOfWorkAutofacHostFactory in your .svc file as
> the service host factory.

}

}

> Hmm, The Behaviors takes in IServiceBehavior rather than
> IEndpointBehavior

> If I set it up to use a ServiceBehavior it get's injected once, and
> never again, I guess that the service behavior is newed up once?

> The same thing happens with the EndPointBehavior.

> I stepped through all the code and it seems that the
> CallContextInitializer is created once, and BeforeInvoke/AfterInvoke
> are called every request, so I would need to pass a IContainer down to
> the CallContextInitializer and resolve a new IUnitOfWork BeforeInvoke
> and commit it AfterInvoke.

> What has confused me is the article relies on the fact that the
> UnitOfWork is created once, and it's role is simply to Open a NH
> Session and Transaction, and Commit it later.

> I want a new UnitOfWork created for each request which wasn't
> happening.

> I think I've solved my problem, it's a little bit work, will have to
> write my own ServiceBehavior, EndpointBehavior, and
> CallContextInitializer, and pass the Autofac IContainer in for it to
> resolve the UnitOfWork, but it will do what I want it to do :)

> On Nov 4, 3:50 am, Travis Illig <travis.il...@gmail.com> wrote:

> > To the best of my knowledge, Autofac doesn't have a feature to do DI into
> > endpoint behaviors, so you'd have to resolve the dependency manually. (Nick
> > will, I'm sure, jump in here and correct me if I'm wrong.) So in your
> > behavior where you need your IUnitOfWork as a constructor parameter, you'd
> > instead resolve it directly:

> > public UnitOfWorkEndpointBehavior()
> > {
> >   this.unitOfWork = AutofacHostFactory.Container.Resolve<IUnitOfWork>();

> > }

> > You can still apply behaviors through XML configuration using Autofac, just
> > like normal, but if you want to do it programmatically you can have a
> > custom host factory based on AutofacServiceHostFactory and use the
> > ConfigurationAction static property

> > UnitOfWorkAutofacHostFactory.ConfigurationAction =
> >   host =>
> >     host.Opening += (sender, args) =>
> >       host.Description.Behaviors.Add(new UnitOfWorkEndpointBehavior());

> > Then specify the custom UnitOfWorkAutofacHostFactory in your .svc file as
> > the service host factory.

> Nope, no luck, passing in the IContainerContext or ILifetimeContext
> and resolving the Unit of Work:

> public object BeforeInvoke(InstanceContext instanceContext,
> IClientChannel channel, Message message)
> {
>     var uow = _container.Resolve<IUnitOfWork>();

>     uow.Begin();

>     return null;

> }

> public void AfterInvoke(object correlationState)
> {
>     var uow = _container.Resolve<IUnitOfWork>();

>     uow.Commit();

> }

> Causes two different instances to be returned. They aren't in the same
> scope. :(

> builder.RegisterType(typeof (UnitOfWork))
>         .As(typeof (IUnitOfWork))
>         .InstancePerLifetimeScope()
>         .OnRelease(x =>
>                         {
>                             ((IUnitOfWork) x).Commit();
>                         });

> This however, seems to work fine. But seems real hacky...

> On Nov 4, 12:10 pm, Phillip Haydon <phillip.hay...@gmail.com> wrote:

> > Hmm, The Behaviors takes in IServiceBehavior rather than
> > IEndpointBehavior

> > If I set it up to use a ServiceBehavior it get's injected once, and
> > never again, I guess that the service behavior is newed up once?

> > The same thing happens with the EndPointBehavior.

> > I stepped through all the code and it seems that the
> > CallContextInitializer is created once, and BeforeInvoke/AfterInvoke
> > are called every request, so I would need to pass a IContainer down to
> > the CallContextInitializer and resolve a new IUnitOfWork BeforeInvoke
> > and commit it AfterInvoke.

> > What has confused me is the article relies on the fact that the
> > UnitOfWork is created once, and it's role is simply to Open a NH
> > Session and Transaction, and Commit it later.

> > I want a new UnitOfWork created for each request which wasn't
> > happening.

> > I think I've solved my problem, it's a little bit work, will have to
> > write my own ServiceBehavior, EndpointBehavior, and
> > CallContextInitializer, and pass the Autofac IContainer in for it to
> > resolve the UnitOfWork, but it will do what I want it to do :)

> > On Nov 4, 3:50 am, Travis Illig <travis.il...@gmail.com> wrote:

> > > To the best of my knowledge, Autofac doesn't have a feature to do DI into
> > > endpoint behaviors, so you'd have to resolve the dependency manually. (Nick
> > > will, I'm sure, jump in here and correct me if I'm wrong.) So in your
> > > behavior where you need your IUnitOfWork as a constructor parameter, you'd
> > > instead resolve it directly:

> > > public UnitOfWorkEndpointBehavior()
> > > {
> > >   this.unitOfWork = AutofacHostFactory.Container.Resolve<IUnitOfWork>();

> > > }

> > > You can still apply behaviors through XML configuration using Autofac, just
> > > like normal, but if you want to do it programmatically you can have a
> > > custom host factory based on AutofacServiceHostFactory and use the
> > > ConfigurationAction static property

> > > UnitOfWorkAutofacHostFactory.ConfigurationAction =
> > >   host =>
> > >     host.Opening += (sender, args) =>
> > >       host.Description.Behaviors.Add(new UnitOfWorkEndpointBehavior());

> > > Then specify the custom UnitOfWorkAutofacHostFactory in your .svc file as
> > > the service host factory.

> I've posted my current solution here if anyone cares :)

> http://www.philliphaydon.com/2011/11/unit-of-work-with-wcf-and-autofac/

> If anyone has any feedback on it, would be appreciated.

> On Nov 4, 2:47 pm, Phillip Haydon <phillip.hay...@gmail.com> wrote:
> > Nope, no luck, passing in the IContainerContext or ILifetimeContext
> > and resolving the Unit of Work:

> > public object BeforeInvoke(InstanceContext instanceContext,
> > IClientChannel channel, Message message)
> > {
> >     var uow = _container.Resolve<IUnitOfWork>();

> >     uow.Begin();

> >     return null;

> > }

> > public void AfterInvoke(object correlationState)
> > {
> >     var uow = _container.Resolve<IUnitOfWork>();

> >     uow.Commit();

> > }

> > Causes two different instances to be returned. They aren't in the same
> > scope. :(

> > builder.RegisterType(typeof (UnitOfWork))
> >         .As(typeof (IUnitOfWork))
> >         .InstancePerLifetimeScope()
> >         .OnRelease(x =>
> >                         {
> >                             ((IUnitOfWork) x).Commit();
> >                         });

> > This however, seems to work fine. But seems real hacky...

> > On Nov 4, 12:10 pm, Phillip Haydon <phillip.hay...@gmail.com> wrote:

> > > Hmm, The Behaviors takes in IServiceBehavior rather than
> > > IEndpointBehavior

> > > If I set it up to use a ServiceBehavior it get's injected once, and
> > > never again, I guess that the service behavior is newed up once?

> > > The same thing happens with the EndPointBehavior.

> > > I stepped through all the code and it seems that the
> > > CallContextInitializer is created once, and BeforeInvoke/AfterInvoke
> > > are called every request, so I would need to pass a IContainer down to
> > > the CallContextInitializer and resolve a new IUnitOfWork BeforeInvoke
> > > and commit it AfterInvoke.

> > > What has confused me is the article relies on the fact that the
> > > UnitOfWork is created once, and it's role is simply to Open a NH
> > > Session and Transaction, and Commit it later.

> > > I want a new UnitOfWork created for each request which wasn't
> > > happening.

> > > I think I've solved my problem, it's a little bit work, will have to
> > > write my own ServiceBehavior, EndpointBehavior, and
> > > CallContextInitializer, and pass the Autofac IContainer in for it to
> > > resolve the UnitOfWork, but it will do what I want it to do :)

> > > On Nov 4, 3:50 am, Travis Illig <travis.il...@gmail.com> wrote:

> > > > To the best of my knowledge, Autofac doesn't have a feature to do DI
> into
> > > > endpoint behaviors, so you'd have to resolve the dependency
> manually. (Nick
> > > > will, I'm sure, jump in here and correct me if I'm wrong.) So in your
> > > > behavior where you need your IUnitOfWork as a constructor parameter,
> you'd
> > > > instead resolve it directly:

> > > > public UnitOfWorkEndpointBehavior()
> > > > {
> > > >   this.unitOfWork =
> AutofacHostFactory.Container.Resolve<IUnitOfWork>();

> > > > }

> > > > You can still apply behaviors through XML configuration using
> Autofac, just
> > > > like normal, but if you want to do it programmatically you can have a
> > > > custom host factory based on AutofacServiceHostFactory and use the
> > > > ConfigurationAction static property

> > > > UnitOfWorkAutofacHostFactory.ConfigurationAction =
> > > >   host =>
> > > >     host.Opening += (sender, args) =>
> > > >       host.Description.Behaviors.Add(new
> UnitOfWorkEndpointBehavior());

> > > > Then specify the custom UnitOfWorkAutofacHostFactory in your .svc
> file as
> > > > the service host factory.

> --
> You received this message because you are subscribed to the Google Groups
> "Autofac" group.
> To post to this group, send email to autofac@googlegroups.com.
> To unsubscribe from this group, send email to
> autofac+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/autofac?hl=en.

}

> Hi Phillip - thanks for the follow up, glad you were able to sort something
> out.

> Nick

> On 5 November 2011 08:23, Phillip Haydon <phillip.hay...@gmail.com> wrote:

> > I've posted my current solution here if anyone cares :)

> >http://www.philliphaydon.com/2011/11/unit-of-work-with-wcf-and-autofac/

> > If anyone has any feedback on it, would be appreciated.

> > On Nov 4, 2:47 pm, Phillip Haydon <phillip.hay...@gmail.com> wrote:
> > > Nope, no luck, passing in the IContainerContext or ILifetimeContext
> > > and resolving the Unit of Work:

> > > public object BeforeInvoke(InstanceContext instanceContext,
> > > IClientChannel channel, Message message)
> > > {
> > >     var uow = _container.Resolve<IUnitOfWork>();

> > >     uow.Begin();

> > >     return null;

> > > }

> > > public void AfterInvoke(object correlationState)
> > > {
> > >     var uow = _container.Resolve<IUnitOfWork>();

> > >     uow.Commit();

> > > }

> > > Causes two different instances to be returned. They aren't in the same
> > > scope. :(

> > > builder.RegisterType(typeof (UnitOfWork))
> > >         .As(typeof (IUnitOfWork))
> > >         .InstancePerLifetimeScope()
> > >         .OnRelease(x =>
> > >                         {
> > >                             ((IUnitOfWork) x).Commit();
> > >                         });

> > > This however, seems to work fine. But seems real hacky...

> > > On Nov 4, 12:10 pm, Phillip Haydon <phillip.hay...@gmail.com> wrote:

> > > > Hmm, The Behaviors takes in IServiceBehavior rather than
> > > > IEndpointBehavior

> > > > If I set it up to use a ServiceBehavior it get's injected once, and
> > > > never again, I guess that the service behavior is newed up once?

> > > > The same thing happens with the EndPointBehavior.

> > > > I stepped through all the code and it seems that the
> > > > CallContextInitializer is created once, and BeforeInvoke/AfterInvoke
> > > > are called every request, so I would need to pass a IContainer down to
> > > > the CallContextInitializer and resolve a new IUnitOfWork BeforeInvoke
> > > > and commit it AfterInvoke.

> > > > What has confused me is the article relies on the fact that the
> > > > UnitOfWork is created once, and it's role is simply to Open a NH
> > > > Session and Transaction, and Commit it later.

> > > > I want a new UnitOfWork created for each request which wasn't
> > > > happening.

> > > > I think I've solved my problem, it's a little bit work, will have to
> > > > write my own ServiceBehavior, EndpointBehavior, and
> > > > CallContextInitializer, and pass the Autofac IContainer in for it to
> > > > resolve the UnitOfWork, but it will do what I want it to do :)

> > > > On Nov 4, 3:50 am, Travis Illig <travis.il...@gmail.com> wrote:

> > > > > To the best of my knowledge, Autofac doesn't have a feature to do DI
> > into
> > > > > endpoint behaviors, so you'd have to resolve the dependency
> > manually. (Nick
> > > > > will, I'm sure, jump in here and correct me if I'm wrong.) So in your
> > > > > behavior where you need your IUnitOfWork as a constructor parameter,
> > you'd
> > > > > instead resolve it directly:

> > > > > public UnitOfWorkEndpointBehavior()
> > > > > {
> > > > >   this.unitOfWork =
> > AutofacHostFactory.Container.Resolve<IUnitOfWork>();

> > > > > }

> > > > > You can still apply behaviors through XML configuration using
> > Autofac, just
> > > > > like normal, but if you want to do it programmatically you can have a
> > > > > custom host factory based on AutofacServiceHostFactory and use the
> > > > > ConfigurationAction static property

> > > > > UnitOfWorkAutofacHostFactory.ConfigurationAction =
> > > > >   host =>
> > > > >     host.Opening += (sender, args) =>
> > > > >       host.Description.Behaviors.Add(new
> > UnitOfWorkEndpointBehavior());

> > > > > Then specify the custom UnitOfWorkAutofacHostFactory in your .svc
> > file as
> > > > > the service host factory.

> > --
> > You received this message because you are subscribed to the Google Groups
> > "Autofac" group.
> > To post to this group, send email to autofac@googlegroups.com.
> > To unsubscribe from this group, send email to
> > autofac+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/autofac?hl=en.

> Hi Nick,

> I think this is an interesting feature for adding into
> Autofac.WcfIntegration, that is the ability to have Autofac handle the
> creation of EndPointBehaviors. I don't know if it is doable and if WCF
> provides the wiring for that, but it sure would be useful... Are there any
> plans for it?

> Btw, and since this is my first time posting here, great job on Autofac,
> absolutely loving it.

> Thanks,
> Kostas

>  --
> You received this message because you are subscribed to the Google Groups
> "Autofac" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/autofac/-/POvGWPCUtpEJ.

> To post to this group, send email to autofac@googlegroups.com.
> To unsubscribe from this group, send email to
> autofac+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/autofac?hl=en.