Skip to main content

A DD4T.net Implementation - Umbrella Models

In a previous post, I was describing how certain Component link fields in a Schema can map to more than just one type of domain model. At the same time, a Multimedia link field in a Schema can allow more than just one Multimedia Schema as its linked Multimedia Component.

In the example below, property RelatedItems could link to either one of models Article, Internal Link or External Link.

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


The same occurs with Multimedia link BinaryAsset, which can link to any of the multimedia class types PDF Document, Excel Document or Work Document.

        public class Software
        {
            /// <summary>
            /// Could be one of PDF Document, Excel Document, Word Document
            /// </summary>
            public BaseModel BinaryAsset { get; set; }


These links are what I called 'umbrella models', which can hold several types of domain models, but for which at compile time, we cannot tell actual type it holds. Therefore, we must use a high level general type like BaseModel and make the differentiation only at run-time, using code like this:

        public static MvcHtmlString Link(this HtmlHelper htmlHelper, BaseModel model)
        {
            if (model is InternalLink)
            {
                // Magic happens here
            }
            else if (model is ExternalLink)
            {
                // Magic happens here
            }


We will see in a next post how we are building these models, and more interestingly, how we build these umbrella models.


Comments

Popular posts from this blog

Toolkit - Dynamic Content Queries

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

A DD4T.net Implementation - Custom Binary Publisher

The default way to publish binaries in DD4T is implemented in class DD4T.Templates.Base.Utils.BinaryPublisher and uses method RenderedItem.AddBinary(Component) . This produces binaries that have their TCM URI as suffix in their filename. In my recent project, we had a requirement that binary file names should be clean (without the TCM URI suffix). Therefore, it was time to modify the way DD4T was publishing binaries. The method in charge with publishing binaries is called PublishItem and is defined in class BinaryPublisher . I therefore extended the BinaryPublisher and overrode method PublishItem. public class CustomBinaryPublisher : BinaryPublisher { private Template currentTemplate; private TcmUri structureGroupUri; In its simplest form, method PublishItem just takes the item and passes it to the AddBinary. In order to accomplish the requirement, we must specify a filename while publishing. This is the file name part of the binary path of Component.BinaryConten

Scaling Policies

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