Detect invalid directives

John Todd <[email protected]>
Newsgroups gmane.comp.web.freemarker.user
Message-ID <[email protected]>
Hello,

  I would like to handle invalid directives however they are just
passing through the templating engine as text, e.g. using the following
FTL "blah.ftl":

This is [#blah]content[/#blah].  This is [#fu] content.

and the code:

public class App {

    public static void main(String[] args) throws Exception {
        Configuration cfg = new Configuration();
        cfg.setTagSyntax(Configuration.SQUARE_BRACKET_TAG_SYNTAX);
       
        cfg.setDirectoryForTemplateLoading(new
File(System.getProperty("user.dir")));
       
        System.out.println("Compiling template: blah.ftl");
        FileReader reader = new
FileReader(System.getProperty("user.dir") + "/blah.ftl");
        // Expect ParseException
        Template template = new Template("blah.ftl", reader, cfg);

        System.out.println("Getting template from Configuration.");
        // Also expect ParseException
        template = cfg.getTemplate("blah.ftl");
        StringWriter writer = new StringWriter();
        template.process(new HashMap(), writer);
        System.out.println("Output: " + writer.toString());
    }
}

I get the output:

This is [#blah]content[/#blah].  This is [#fu] content.

In each Template reference, I'm expecting a compilation error w/
"Unknown directive" per the FMParser.jj grammar.  Any suggestions?

Thanks,

John T.







------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.