Skip to main content

Toolkit - Custom Tags Execution while Assembling

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

This post presents the TagFactory in charge with execution of custom tags for the Toolkit Component Presentations.

The content of Dynamic Component Presentations can contain custom tags in the form of <mytag>some body</mytag>. These XML-like nodes are backed by a Java class that is executed when the tag is rendered.

The configuration of tag names and Java class name is done in file toolkit.properties. More information is available in post Installation and Configuration.

The custom tag support uses the following concepts:
  • TagFactory -- the entry point into execution of tags for a piece of content;
  • TagSupport -- class that associates a tag name with a tag implementation class;
  • TagRenderer -- interface that a tag implementation class must implement;

TagRenderer Interface

This is the interface that any tag class must implement. It contains only one method, doTag that is called by the TagSupport class when the tag is executed.

public interface TagRenderer {
    String doTag(String tagBody);
}

A simple example tag follows:

public class MyTag implements TagRenderer {
    public String doTag(String tagBody) {
        return tagBody.toUpperCase();
    }
}

TagSupport Class

This class represents an association between a tag name and a tag implementing class. The only operation this class defines is an execute(String) method. This calls method doTag(String) on the tag implementing class (the one that extends TagRenderer).

Each TagSupport contains a Regular Expression on the name of the tag, using simple pattern like <%1$s[^>]*>(.*)</%1$s>. The Regular Expression identifies the tag XML-like pattern and allows the extraction of the body for further processing.

public String execute(String tagBody) {
    try {
        return clazz.newInstance().doTag(tagBody);
    } catch (IllegalAccessException | InstantiationException e) {
        throw new TagException(e);
    }
}

TagFactory Class

The TagFactory is a singleton that contains an array of TagSupport objects. This array represents all the tags configured in file toolkit.properties.

Method executeTags(String) iterates over each tag and applies its pattern to the String content passed as parameter. For each match of the tag pattern in the content, it calls the tag's execute(String) method passing as parameter the identified tag body.

The original tag is then replaced with the result of its execution.

public String executeTags(String content) {
    StringBuffer result = null;
    StringBuffer buffer = new StringBuffer(content);

    for (TagSupport tag : tags) {
        result = new StringBuffer();
        Matcher matcher = tag.getPattern().matcher(buffer);
        while (matcher.find()) {
            String tagBody = matcher.groupCount() > 0 ? matcher.group(1) : null;
            matcher.appendReplacement(result, tag.execute(tagBody));
        }
        matcher.appendTail(result);
        buffer = result;
    }

    return result == null ? content : result.toString();
}



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