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

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

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

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...