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/26 17:01:16 UTC
[jira] Resolved: (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 resolved CLK-568.
-------------------------------
Resolution: Fixed
fixed in trunk
> 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
> Fix For: 2.1.0
>
> 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.