Skip to main content

A DD4T.net Implementation - Dependency Injection

Image
By
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();




Labels:

Comments

Post a Comment

Popular posts from this blog

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
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
1 comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more