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

Toolkit - Performance

By
This post if part of a series about the File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents performance data that was captured for each major functionality with and without caching Linking, CP Assembler, Component Presentation Factory, Dynamic Content Queries, Model Factory. The data was captured on a 2014 Macbook Pro 15", 16 GB RAM, 2.6 GHz Intel Core i7 running OS X El Capitan. Test methodology: each test was run for 3 minutes and the total number of successful Toolkit API calls was measured. Then the number of calls per second was computed 'with cache' and 'without cache' test runs. Then a cache boost factor was calculated by diving (the number of API calls with cache) / (number of API calls without cache). Each cache test was executed 3 times, with different cache time-to-live values of 1 second, 5 seconds and 0 seconds (eternal cache, no expiration). The rationale is to see what impact different cache expiration/evi...
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...
2 comments
Read more

A Core Service Java Client

By Unknown
I have seen many times the creation of a .NET client for SDL Tridion's Core Service, but not once a Java client. In .NET / Visual Studio is extremely easy to create the proxy classes based on the service's WSDL. So how hard can it be in Java? The entire code in this example is available in my Google Code project . Which Tool? Doing a bit of research on the multiple ways of creating Java proxy classes for web services left me quite confused as to which framework / utility to use. They are quite a few (AXIS, JAXB, Apache CXF, XFire, NetBeans plugin, IDEA plugin, Eclipse plugin, etc). They seemed to be cumbersome to use, too specific, limited, quirky, buggy, etc. What I wanted was a simple generic too that worked. Enter wsimport.exe ... Generating the Proxies Note: Check out the update post available here  http://yatb.mitza.net/2012/12/java-core-service-trouble-with-datetime.html Wsimport.exe is part of the JDK (mine is located in C:\Progrm Files\Java\jdk1.6.0_33\bin ),...
3 comments
Read more