Skip to main content

A DD4T.net Implementation - Umbrella Model Builders

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


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

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

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