Mailing-List: contact click-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: click-dev@incubator.apache.org
Message-ID: <1490068928.1248620476429.JavaMail.jira@brutus>
Date: Sun, 26 Jul 2009 08:01:16 -0700 (PDT)
From: "Bob Schellink (JIRA)" <jira@apache.org>
To: click-dev@incubator.apache.org
Subject: [jira] Resolved: (CLK-568) Add ability to use templates with custom
 extensions
In-Reply-To: <1957600703.1247761874980.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.