You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Bob Schellink (JIRA)" <ji...@apache.org> on 2009/07/16 18:33:15 UTC

[jira] Updated: (CLK-568) Add ability to use templates with custom extensions

     [ https://issues.apache.org/jira/browse/CLK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Schellink updated CLK-568:
------------------------------

    Attachment: istemplate.patch

Attached is a patch for this issue. It is heavily commented, but only about 6 lines of code to implement.

> Add ability to use templates with custom extensions
> ---------------------------------------------------
>
>                 Key: CLK-568
>                 URL: https://issues.apache.org/jira/browse/CLK-568
>             Project: Click
>          Issue Type: New Feature
>          Components: core
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>         Attachments: istemplate.patch
>
>
> A recurring question on the user list is the ability to map alternative extensions as Page class templates instead of the default ".htm".
> We could add a method ConfigService#isTemplate(String path), that can be invoked (at app startup) to check if a template is .htm/.jsp. Users can then override this single method to map alternative extensions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.