Skip to main content

Toolkit - Dynamic Linking

This post if part of a series about the File System Toolkit - a custom content delivery API for SDL Tridion.

In this post I describe the dynamic link resolving logic as part of the Link Factory.

There are three types of links: Component, Page and Binary links. Each of these links can be resolved using the Link Factory.

Component Link

Resolving a Component link implies finding the URL of the Page the target Component appears on. Using the current Toolkit models, it is quite straight forward to retrieve the URL, because the link information is contained within the Component model.

However, there might be several potential links available when performing Component link resolving. Namely, there can be several cases possible:
  • there is no linking information available in the Component model -- this means the link cannot be resolved (i.e. there is no Page published that contains the given Component);
  • there is exactly one Page available that contains the Component -- this means we retrieve the Page URL and return it as the link;
  • there are several potential Pages available that contain the Component -- in this case we need to pick one page only according to the following algorithm: 
    • take the Page that contains the Component with the highest link priority. If there are more than one pages possible, then go to next step;
    • take the Page relatively closest to the Page where the link is displayed on. The relative distance is the number of folders one page is away from the other. If there are more than one pages possible, then go to next step;
    • take the page that was published the latest;
You might notice that in order for the algorithm to work, we must provide the current Page -- this is the page where the link is displayed on. Without this page, we cannot identify accurately the relatively closest potential page.

public Link getComponentLink(TcmUri pageUri, TcmUri componentUri) {
    LinkImpl result = new LinkImpl();
    ComponentMeta componentMeta = modelFactory.getModel(componentUri);
    List<LinkInfo> linkInfos = componentMeta.getLinkInfos();
    if (linkInfos == null || linkInfos.size() == 0) {
        return result;
    }

    String[] urlParts;
    PageMeta pageMeta = modelFactory.getModel(pageUri);
    if (pageMeta == null) {
        urlParts = new String[0];
    } else {
        urlParts = pageMeta.getUrl().split("/");
    }

    int pageId = pageUri.getItemId();
    int maxPriority = 1;
    int minDistance = Integer.MAX_VALUE;
    List<LinkInfo> filteredInfos = new ArrayList<>();

    for (LinkInfo linkInfo : linkInfos) {
        if (linkInfo.getPage() != pageId) {
            int distance = getDistance(urlParts, linkInfo.getUrl());
            int priority = linkInfo.getPriority();
            if (priority > maxPriority) {
                maxPriority = priority;
                minDistance = distance;
                filteredInfos.clear();
            } else if (distance < minDistance) {
                minDistance = distance;
                filteredInfos.clear();
            }
            if (priority == maxPriority && distance == minDistance) {
                filteredInfos.add(linkInfo);
            }
        }
    }

    LinkInfo linkInfo = getLastPublished(filteredInfos);
    if (linkInfo != null) {
        result.setResolved(true);
        result.setUrl(linkInfo.getUrl());
        result.setTargetUri(new TcmUri(componentUri.getPublicationId(),
                linkInfo.getPage(), ItemTypes.PAGE));
    }

    return result;
}

Below are the two helper methods getDistance between two paths and getLastPublished date out of a collection of Pages.

private int getDistance(String[] parts, String url) {
    int result = 0;

    String[] parts2 = url.split("/");
    int n = Math.min(parts.length, parts2.length) - 1;
    int i = 0;
    boolean loop = true;

    for (; i < n && loop; i++) {
        if (!parts[i].equals(parts2[i])) {
            loop = false;
            i--;
        }
    }

    result += parts.length - i - 1;
    result += parts2.length - i - 1;

    return result;
}

private LinkInfo getLastPublished(List<LinkInfo> linkInfos) {
    switch (linkInfos.size()) {
        case 0:
            return null;

        case 1:
            return linkInfos.get(0);

        default:
            long maxPublished = 0;
            LinkInfo result = linkInfos.get(0);

            for (LinkInfo linkInfo : linkInfos) {
                TcmUri metaUri = new TcmUri(linkInfo.getPublication(), linkInfo.getPage(), ItemTypes.PAGE);
                PageMeta pageMeta = modelFactory.getModel(metaUri);
                if (pageMeta != null) {
                    long lastPublished = pageMeta.getLastPublished().getTime();
                    if (lastPublished > maxPublished) {
                        maxPublished = lastPublished;
                        result = linkInfo;
                    }
                }
            }

            return result;
    }
}

Page Links

Resolving a page link implies retrieving the Page model by TcmUri and returning its URL.

public Link getPageLink(TcmUri pageUri) {
    LinkImpl result = new LinkImpl();
    PageMeta pageMeta = modelFactory.getModel(pageUri);
    if (pageMeta == null) {
        return result;
    }

    result.setResolved(true);
    result.setUrl(pageMeta.getUrl());
    result.setTargetUri(pageMeta.getTcmUri());

    return result;
}

Binary Links

Resolving a binary link implies retrieving the Multimedia Component model and retrieving its link information URL. Binaries can be published using different variants, so we can either identify a link by its variant or, in the absence of a variant, simply serve the first link available.

public Link getBinaryLink(TcmUri binaryUri, String variant) {
    LinkImpl result = new LinkImpl();
    ComponentMeta binaryMeta = modelFactory.getModel(binaryUri);
    if (binaryMeta == null) {
        return result;
    }

    if (!binaryMeta.isMultimedia()) {
        return result;
    }

    List<LinkInfo> linkInfos = binaryMeta.getLinkInfos();
    if (linkInfos == null || linkInfos.size() == 0) {
        return result;
    }

    variant = variant == null ? "" : variant;

    for (LinkInfo linkInfo : linkInfos) {
        String linkVariant = linkInfo.getVariant();
        linkVariant = linkVariant == null ? "" : linkVariant;
        if (variant.equals(linkVariant)) {
            result.setResolved(true);
            result.setUrl(linkInfo.getUrl());
            result.setTargetUri(binaryUri);
            break;
        }
    }

    return result;
}



Comments

Popular posts from this blog

Toolkit - Performance

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

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

A Core Service Java Client

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