Skip to main content

A DD4T.net Implementation - Umbrella Model Builders

In a previous post I was presenting Umbrella Models and what they are useful for in DD4T. To recap a bit, we need these generic models when we have Component or Multimedia Links that can point to components based on several Schemas. In such case, we can't say for sure what is the type of the linked Component, and instead we need to use type ModelBase (presented in this post).

In this post I'll present the builders for such polymorphic links. Let's first assume we have a Device model that has a Component link field that accepts several Schemas:

    public class Device : ModelBase
    {
        /// <summary>
        /// Could be a heterogenous collection of: Internal Link, External Link
        /// </summary>
        public IList<ModelBase> RelatedItems { get; set; }


The Device model builder needs to be able to identify the type of the linked RelatedItems and build the right model for it. As such, we have the following code in the DeviceBuilder class:

    Device device = new Device(component)
    {
        RelatedItems = RelatedItemBuilder.Instance.Build(fields.LinkedComponentValues("Right_Related_Items"))


The code simply invokes an umbrella builder (i.e. RelatedItemBuilder) that knows how to build the actual model Internal Link or External Link. The umbrella builder sample code looks like this:

    public class RelatedItemBuilder : Builder<IComponent, ModelBase>
    {
        private static readonly RelatedItemBuilder _instance = new RelatedItemBuilder();
        public static RelatedItemBuilder Instance { get { return _instance; } }

        private RelatedItemBuilder() {}

        public override ModelBase Build(IComponent component)
        {
            ModelBase model = null;

            switch (component.Schema.Title)
            {
                case Constants.INTERNAL_LINK_SCHEMA:
                    model = InternalLinkBuilder.Instance.Build(component);
                    break;

                case Constants.EXTERNAL_LINK_SCHEMA:
                    model = ExternalLinkBuilder.Instance.Build(component);
                    break;
            }

            return model;
        }


In this case I chose to filter the type of a Component based on its Schema title. A better solution would be to filter based on Schema root element name. This is not always possible, because the root element name must be changed proactively at the moment when the Schema is created or at least before creating many Components on it.

Based on the Schema title (or root element name), we identify the right builder and, as such, we invoke the respective builder.


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