Skip to main content

DynamicContent REL Tag Addition to OData Query Extension

The current post is a follow-up of the previous OData Query Extension I had developed for Tridion 2011 and 2013:
The code for this version is available in my GitHub project, distributable JAR (odata-query-extension-1.3.jar).

DynamicContent REL Tag

This tag queries for dynamic Component Presentations using the CD API Query and Criterias. It accepts the following attributes:

<tridion:dynamiContent var="namefilter="exprorderby="exprtop="intskip="int"
    componentTemplate="tcmuri" />

, where:
  • var - name of the TransformContext variable that would hold the result. If var is specified, the resulting array of ComponentPresentation objects is stored into the TransformContext; otherwise, the DCPs are output one after the oter;
  • filter - expression specifying the Criterias to query by. The format of this attribute is the same as the $filter query parameter presented in URL Syntax for OData Query Extension;
  • orderby - expression specifying the order to sort results by. The format of this attribute is the same as the $orderby query parameter presented in URL Syntax for OData Query Extension;
  • top - if specified, only returns the first top results;
  • skip - if specified, skip the first skip results;
  • componentTemplate - if specified, only return Component Presentations based on this Component Template;
<tridion:dynamicContent filter="ItemModificationDate gt '2013-05-01 13:24:56.999'"
    orderby="ItemTitle ItemModification asc" />


  • Copy the JAR (odata-query-extension-1.3.jar) to your WEB-INF/lib folder (or /bin/lib for .NET installations);
  • Edit your cd_dynamic_conf.xml and add the following line just below the <TCDLEngine>:
    <TagBundle Resource="odata-query-extension.xml" />

Save the Good Part Last - The Code

DynamicContentTagRenderer Class

public int doStartTag(Tag tag, StringBuffer tagBody, TransformContext context, OutputDocument target)
        throws TCDLTransformerException {
    DynamicContent dynamicContent = new DynamicContent(parametersMap);
    dcps = dynamicContent.queryComponentPresentations();

    return dcps.length > 0 ? Tag.CONTINUE_TAG_EVALUATION : Tag.SKIP_TAG;

public String doEndTag(Tag tag, StringBuffer tagBody, TransformContext context, OutputDocument target)
        throws TCDLTransformerException {
    if (var == null) {
        int publicationId = dcps[0].getPublicationId();
        ComponentPresentationAssembler assembler = new ComponentPresentationAssembler(publicationId);
        for (ComponentPresentation dcp : dcps) {
            tagBody.append(assembler.getContent(dcp.getComponentId(), dcp.getComponentTemplateId()));
    } else {
        context.set(var, dcps);

    return tagBody.toString();

DynamicContent Class

public DynamicContent(Map<String, String> attributes) {
    QueryBuilder builder = new QueryBuilder(attributes);
    query = builder.getQuery();

public ComponentPresentation[] queryComponentPresentations() {
    List<ComponentPresentation> result = new ArrayList<ComponentPresentation>();

    try {
        String componentTcmUris[] = query.executeQuery();
        log.debug("Query found " + componentTcmUris.length + " Components");
        if (componentTcmUris.length == 0) {
            return new ComponentPresentation[0];

        TCMURI tcmUri = new TCMURI(componentTcmUris[0]);
        int publicationId = tcmUri.getPublicationId();
        String templateTcmUri = getTemplateTcmUri(publicationId);

        ComponentPresentationFactory factory = new ComponentPresentationFactory(publicationId);
        ComponentPresentation componentPresentation;

        for (String componentTcmUri : componentTcmUris) {
            if (templateTcmUri == null) {
                componentPresentation = factory.getComponentPresentationWithHighestPriority(componentTcmUri);
            } else {
                componentPresentation = factory.getComponentPresentation(componentTcmUri, templateTcmUri);
            if (componentPresentation != null) {
    } catch (StorageException se) {
        log.error("StorageException occurred", se);
    } catch (ParseException pe) {
        log.error("ParseException occurred", pe);

    return result.toArray(new ComponentPresentation[0]);


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: I stumbled upon the following post from 2008 (!!!), , 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

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven