You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@turbine.apache.org by "Thomas Vandahl (JIRA)" <ji...@apache.org> on 2008/03/30 18:09:25 UTC

[jira] Closed: (TRB-25) Remove Turbines Dependeny upon Velocity

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

Thomas Vandahl closed TRB-25.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s: Core 2.3.3
         Assignee: Thomas Vandahl

Actually, Turbine does support different templating solutions. Dependencies on Velocity only exist for classes which provide Velocity-derived services, such as VelocitySecureScreen, VelocitySecureAction etc. So the usage of the Velocity class "Context" makes perfect sense to me.

Other implementations such as JSP are available without the exact need of needing Velocity features.

> Remove Turbines Dependeny upon Velocity
> ---------------------------------------
>
>                 Key: TRB-25
>                 URL: https://issues.apache.org/jira/browse/TRB-25
>             Project: Turbine
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jürgen Hoffmann
>            Assignee: Thomas Vandahl
>            Priority: Minor
>             Fix For: Core 2.3.3
>
>
> Couldn't we wrap a TurbineContext around a VelocityContext, to receive better abstraction of the Context? Does something like this make sense? I know there has been a lot of discussion around the subject upon the list. Or doesn't it really make sense to have turbine support other templating solutions as well?

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