Skip to main content

A DD4T.net Implementation - A Dynamic Publication Resolver

In the previous post Simple Publication Resolver, I presented a simplistic way of putting generic pages into Publication context by identifying the Publication URL by just applying a regular expression to the URL path.

In this post, I present a proper Publication Resolver algorithm, for DD4T.net, that dynamically maps Publication IDs to Publication URLs and vice versa.

The interface of a Publication Resolver defines 2 methods: GetPublicationUrl and GetPublicationId, which provide retrieval functionality for mapped Publication ID and URL.

public interface IPublicationResolver
{
    string GetPublicationUrl(int publicationId);
    int GetPublicationId(string publicationUrl);
}

The implementing class, PublicationResolver, defines an algorithm that dynamically discovers the mapped ID for a given Publication URL and the other way around. It makes use of the Tridion Content Delivery API PublicationMetaFactory to retrieve the PublicationMeta object containing information about the given Publication:

public class PublicationResolver : IPublicationResolver
{
    private readonly IDictionary<string, int> mapUrlToId =
        new Dictionary<string, int>();
    private readonly IDictionary<int, string> mapIdToUrl =
        new Dictionary<int, string>();

    public string GetPublicationUrl(int publicationId)
    {
        if (mapIdToUrl.ContainsKey(publicationId))
        {
            return mapIdToUrl[publicationId];
        }
        else
        {
            PublicationMetaFactory factory = new PublicationMetaFactory();
            PublicationMeta meta = factory.GetMeta(publicationId);
            string url = meta == null ? string.Empty : meta.PublicationUrl;

            mapIdToUrl[publicationId] = url;
            mapUrlToId[url] = publicationId;

            return url;
        }
    }

    public int GetPublicationId(string publicationUrl)
    {
        if (mapUrlToId.ContainsKey(publicationUrl))
        {
            return mapUrlToId[publicationUrl];
        }
        else
        {
            PublicationMetaFactory factory = new PublicationMetaFactory();
            PublicationMeta meta = factory.GetMetaByPublicationUrl(publicationUrl).FirstOrDefault();
            int id = meta == null ? 0 : meta.Id;

            mapIdToUrl[id] = publicationUrl;
            mapUrlToId[publicationUrl] = id;

            return id;
        }
    }
}

The interface and class above can easily be put in Ninject as singleton mapping:

Bind<IPublicationResolver>().To<PublicationResolver>().InSingletonScope();

When using the Publication Resolver, we can easily retrieve Publication ID for a given URL or the other way around. The code below defines property PublicationResolver that is injected into the current class:

[Inject]
public virtual IPublicationResolver PublicationResolver { get; set; }

...

string url = PublicationResolver.GetPublicationUrl(44);
int id = PublicationResolver.GetPublicationId("/zh/cn/");


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...

I Have Gone Dark

Maybe it's the Holidays, but my mood has gone pretty dark. That is, regarding the look and feel of my computer and Tridion CME, of course. What I did was to dim the lights on the operating system, so I installed Placebo themes for Windows 7 . I went for the Ashtray look -- great name :) My VM looks now like this: But, once you change the theme on Windows, you should 'match' the theme of your applications. Some skin easily, some not. The Office suite has an in-built scheme, which can be set to Black , but it doesn't actually dim the ribbon tool bars -- it looks quite weird. Yahoo Messenger is skinnable, but you can't change the big white panels where you actually 'chat'. Skype is not skinnable at all. For Chrome, there are plenty of grey themes. Now i'm using Pro Grey . But then I got into changing the theme of websites. While very few offer skinnable interfaces (as GMail does), I had to find a way to darken the websites... Enter Stylish -- a pl...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...