[
https://issues.apache.org/struts/browse/WW-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41465
]
Brian Pontarelli commented on WW-1832:
--------------------------------------
I'm not certain that I agree with the production argument. That is because of a
FreeMarker problem with caching correct? In most cases I feel that production
applications should be able to define ONLY the template they are using and not
be forced to pull in the hierarchy of templates they depend on. This also makes
sense for component architectures where components will ship their view objects
(FreeMarker templates probably) as well as the template/themes they will be
using for their forms.
Therefore, I would expect that this would allow a template to be defined
partially or fully within the project and everything else to be defined within
JAR files. Furthermore, if there truly is a large performance hit with
FreeMarker templates inside JAR files, I feel that needs to be fixed as well.
Of course, this is all mainly due to my work with Smart URLs plugin and
building a component framework on top of Struts.
> Template directory config (struts.ui.templateDir) causes all templates to
> fail completely
> -----------------------------------------------------------------------------------------
>
> Key: WW-1832
> URL: https://issues.apache.org/struts/browse/WW-1832
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.6
> Reporter: Brian Pontarelli
> Priority: Critical
> Fix For: 2.1.0
>
>
> There are a number of issues regarding themes that need to be addressed. All
> of these issues stem from the fact that Struts2 allows a property to move the
> location of the theme overrides from /template to anywhere within the web
> application. Setting it to something like this causes nothing to work at all.
> struts.ui.templateDir=/WEB-INF/template
> The first issue is that overrides no longer work because this directory is
> assumed to be the directory for ALL templates including the base template
> being overridden. All path variables no longer work and the theme no does not
> pick up templates from its parent.
> The second issue is that some variables are no longer being set, such as the
> themeProperties.parent. This is obviously due to the directory problem, but
> effects every template file.
> So, for all intents and purposes, this configuration parameter doesn't work
> at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
