Skip to main content

A DD4T.net Implementation - Dependency Injection

As promised in a previous post, I'll talk a bit about the dependency injection, and namely about using Ninject with DD4T .net.

First, I'm not going to attempt to compete with Rob's post about Using Ninject with DD4T. On the contrary, I'm completely piggy-backing on Rob's implementation with a twist of my own. So, in case you wonder how to setup Ninject in DD4T, please check his blog post.

In my implementation, I'm using the Factory pattern a lot. I have many interfaces that have their own implementing classes, then for each such interface, I provide a factory that builds and returns the right object.

Even further, I'm creating interfaces for these factories and then I bind them using Ninject. And Ninject does a great job in helping out here. These factories need to be singletons, in order to save resources and maximize performance. A factory does not keep state; instead, it takes all its settings from the parameters sent to its method. Ninject makes it extremely easy to define singletons, rather than just implement the singleton pattern on your own.

Let's take the example of the ModelFactory that was discussed earlier in this post. Initially I defined the interface IModelFactory:

    public interface IModelFactory
    {
        T GetModel<T>(string componentUri, string viewOrTemplateUri) where T : ModelBase;
        T GetModel<T>(IComponent component) where T : ModelBase;
        T ResolveModel<T>(T model, string viewOrTemplateUri) where T : ModelBase;
        IList<T> ResolveModels<T>(IList<T> models, string viewOrTemplateUri) where T : ModelBase;
    }


Then I created the implementing class, the ModelFactory itself:

    public class ModelFactory : IModelFactory
    {
        public ModelFactory()
        {
            ...
        }

        public T GetModel<T>(string componentUri, string viewOrTemplateUri) where T : ModelBase
        {
            ...
        }

        public T GetModel<T>(IComponent component) where T : ModelBase
        {
            ...
        }

        public T ResolveModel<T>(T model, string viewOrTemplateUri) where T : ModelBase
        {
            ...
        }

        public IList<T> ResolveModels<T>(IList<T> models, string viewOrTemplateUri) where T : ModelBase
        {
            ...
        }
    }


Since the ModelFactory should be a singleton, I decided to bind it to its interface using Ninject:

    public class DD4TNinjectModule : NinjectModule
    {
        public override void Load()
        {
            ...

            Bind<IModelFactory>().To<ModelFactory>().InSingletonScope();
        }
    }


This gives me the assurance that the ModelFactory is a singleton that I can access from anywhere in my application by using the following construct:

    _modelFactory = DependencyResolver.Current.GetService<IModelFactory>();


which works great in a lazy initialisation property:

    private IModelFactory _modelFactory;
    public IModelFactory ModelFactory
    {
        get
        {
            if (_modelFactory == null)
            {
                _modelFactory = DependencyResolver.Current.GetService<IModelFactory>();
            }
            return _modelFactory;
        }
        set { _modelFactory = value; }
    }


But the thing that I like the most about Ninject is the way one can specify Injection Patterns, namely the Initialization Methods and Property Setter Injection. Let's assume the ModelFactory class has some properties that should be 'injected' just after the ModelFactory singleton instance is created. Ninject can handle this elegantly, by simply specifying the annotation attribute [Ninject] before the property declaration.

    [Inject]
    public virtual IComponentFactory ComponentFactory { get; set; }


Property ComponentFactory of class ModelFactory is required during model construction. Since class ModelFactory is instantiated by Ninject, we need Ninject to also set the appropriate ComponentFactory instance. The code above does just that, simply, elegantly and looking a lot like the Spring's @Autowired annotation.

However, in order for this [Inject]-ed property to have a value, we must first define a binding in for interface IComponentFactory. We do that by the following line in DD4TNinjectModule:

    Bind<IComponentFactory>().To<CachingComponentFactory>().InSingletonScope();




Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven