Skip to main content

A DD4T.net Implementation - Navigation (part 3)

Check out the previous posts about the NavigationFactory: Navigation and Navigation (part 2). I presented a way to deserialize the navigation XML into an object model and then serve it through a factory class that uses caching.

In this post, I will present a simple way of locating a certain node in the navigation object model. Locating a NavigationItem is done by comparing it in some way to a given identifier. The most natural way is to retrieve an item by its TcmUri.

In order to do so, I defined the following method on the INavigationFactory interface:

    NavigationItem GetItemById(Navigation navigation, string tcmUri);

The implementation of this method traverses the Navigation object passed as parameter and applies a Comparator to it, hoping to identify the given tcmUri.

The method calls helper method FindItem that performs the recursive traversal of the Navigation object model.

public NavigationItem GetItemById(Navigation navigation, string pageUri)
{
    if (navigation == null)
    {
        return null;
    }

    IComparator comparator = new UriComparator() { Uri = pageUri };
    foreach (NavigationItem item in navigation.Items)
    {
        NavigationItem result = FindItem(item, comparator);
        if (result != null)
        {
            return result;
        }
    }

    return null;
}

The UriComparator class is an implementation of the custom interface IComparator that compares the given Uri property to the TcmUri property of the NavigationItem we are currently testing.

private interface IComparator
{
    bool Compare(NavigationItem item);
}

private class UriComparator : IComparator
{
    public string Uri { get; set; }

    public bool Compare(NavigationItem item)
    {
        return Uri != null && item != null && Uri.Equals(item.TcmUri);
    }
}

Finally, the FindItem method calls the actual comparator's Compare method and performs the depth-first recursive traversal of the NavigationItem passed to it.

private NavigationItem FindItem(NavigationItem item, IComparator comparator)
{
    if (item == null)
    {
        return null;
    }

    if (comparator.Compare(item))
    {
        return item;
    }

    if (item.ChildItems != null)
    {
        foreach (NavigationItem child in item.ChildItems)
        {
            NavigationItem result = FindItem(child, comparator);
            if (result != null)
            {
                return result;
            }
        }
    }

    return null;
}

As an example, the calling code uses the NavigationFactory.GetItemById() in the following way:

INavigationFactory navigationFactory =
        DependencyResolver.Current.GetService<INavigationFactory>();
NavigationItem item = navigationFactory.GetItemById(Navigation, "tcm:1-2-64");


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