You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Sami Dalouche (JIRA)" <ji...@apache.org> on 2007/05/31 23:04:38 UTC

[jira] Created: (WW-1961) Theme inheritance mechanism doesn't work when using the freemarker templates in WEB_APP root.

Theme inheritance mechanism doesn't work when using the freemarker templates in WEB_APP root.
---------------------------------------------------------------------------------------------

                 Key: WW-1961
                 URL: https://issues.apache.org/struts/browse/WW-1961
             Project: Struts 2
          Issue Type: Bug
         Environment: Struts 2.0.8-SNAPSHOT, but same problem with 2.0.6, using Linux, Jetty plugin for maven2
            Reporter: Sami Dalouche
            Priority: Critical


The performance tuning guide suggests copying the template folder to WEB_APP root.

So, I did it, and ajusted the "struts.ui.templateDir" configuration item.
=> drastic improvement of the performance (yiiii ahhhh !! Struts2 is finally faaaast )

However, it seems to break the inheritance mechanism of templates. For instance, the a, a-close , or actionerror tags do not work for the css_xhtml theme (which inherits these tags fro xhtml).

The error is the following one :
[ERROR] [2007-05-31 21:10:26,281] [org.apache.struts2.components.ClosingUIBean] (btpool0-2,) : Could not open template
java.io.FileNotFoundException: Template /struts2-template/css_xhtml/a.ftl not found.

PS: why is it necessary to copy the freemarker template manually to the webapp root to improve performance ? Isn't it possible to inject artificial dates to classpath resources ? The date could depend on devMode = true or false. If true, inject new Date(), if false, inject any really old date. 

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


[jira] Updated: (WW-1961) Theme inheritance mechanism doesn't work when using the freemarker templates in WEB_APP root.

Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Husted updated WW-1961:
---------------------------

    Fix Version/s: Future

Setting Fix Version to "future" for issues without a set fix version. 


> Theme inheritance mechanism doesn't work when using the freemarker templates in WEB_APP root.
> ---------------------------------------------------------------------------------------------
>
>                 Key: WW-1961
>                 URL: https://issues.apache.org/struts/browse/WW-1961
>             Project: Struts 2
>          Issue Type: Bug
>         Environment: Struts 2.0.8-SNAPSHOT, but same problem with 2.0.6, using Linux, Jetty plugin for maven2
>            Reporter: Sami Dalouche
>            Priority: Critical
>             Fix For: Future
>
>
> The performance tuning guide suggests copying the template folder to WEB_APP root.
> So, I did it, and ajusted the "struts.ui.templateDir" configuration item.
> => drastic improvement of the performance (yiiii ahhhh !! Struts2 is finally faaaast )
> However, it seems to break the inheritance mechanism of templates. For instance, the a, a-close , or actionerror tags do not work for the css_xhtml theme (which inherits these tags fro xhtml).
> The error is the following one :
> [ERROR] [2007-05-31 21:10:26,281] [org.apache.struts2.components.ClosingUIBean] (btpool0-2,) : Could not open template
> java.io.FileNotFoundException: Template /struts2-template/css_xhtml/a.ftl not found.
> PS: why is it necessary to copy the freemarker template manually to the webapp root to improve performance ? Isn't it possible to inject artificial dates to classpath resources ? The date could depend on devMode = true or false. If true, inject new Date(), if false, inject any really old date. 

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


[jira] Closed: (WW-1961) Theme inheritance mechanism doesn't work when using the freemarker templates in WEB_APP root.

Posted by "James Holmes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Holmes closed WW-1961.
----------------------------

    Resolution: Duplicate

Closing this as it is a duplicate of WW-1832.

> Theme inheritance mechanism doesn't work when using the freemarker templates in WEB_APP root.
> ---------------------------------------------------------------------------------------------
>
>                 Key: WW-1961
>                 URL: https://issues.apache.org/struts/browse/WW-1961
>             Project: Struts 2
>          Issue Type: Bug
>         Environment: Struts 2.0.8-SNAPSHOT, but same problem with 2.0.6, using Linux, Jetty plugin for maven2
>            Reporter: Sami Dalouche
>            Priority: Critical
>             Fix For: Future
>
>
> The performance tuning guide suggests copying the template folder to WEB_APP root.
> So, I did it, and ajusted the "struts.ui.templateDir" configuration item.
> => drastic improvement of the performance (yiiii ahhhh !! Struts2 is finally faaaast )
> However, it seems to break the inheritance mechanism of templates. For instance, the a, a-close , or actionerror tags do not work for the css_xhtml theme (which inherits these tags fro xhtml).
> The error is the following one :
> [ERROR] [2007-05-31 21:10:26,281] [org.apache.struts2.components.ClosingUIBean] (btpool0-2,) : Could not open template
> java.io.FileNotFoundException: Template /struts2-template/css_xhtml/a.ftl not found.
> PS: why is it necessary to copy the freemarker template manually to the webapp root to improve performance ? Isn't it possible to inject artificial dates to classpath resources ? The date could depend on devMode = true or false. If true, inject new Date(), if false, inject any really old date. 

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