Re: struts 2.3.16 custom (sub-classed) theme issue

osm! Yes, there was bug in 2.3.16 and previous - template folder had to be put on classpath (src/main/resources/) as ThemeManager was looking for theme.properties only using classpath. I have extended that and now (as from 2.3.17 - not released yet) you can put it in webapps as well. See https://

Re: struts 2.3.16 custom (sub-classed) theme issue

Hi Lukasz, Just to follow-up, I *think* I identified the problem... I just don't understand why. The issue is that our template directory is in src/main/webapps/ and not src/main/resources/ . Is it possible that this is a bug in how the UIBean resolves paths? When we move the directory the erro

Re: struts 2.3.16 custom (sub-classed) theme issue

Hi Lukasz, Our case is slightly different... we have about 10 files in our theme. None of our theme files reference a local version of css.ftl. But to reduce the problem to its simplest, if we remove everything from src/main/webapp/template/tdar/ except for theme.properties and textarea.ftl, we s

Re: struts 2.3.16 custom (sub-classed) theme issue

As I understand you have created a custom theme with only one template - textarea.ftl and there isn't neither controlheader.ftl nor controlfooter.ftl in your them? If so, you must use ${parameters.expandTheme} instead of ${parameters.theme} to tell ThemeManager to check current theme and then pare

struts 2.3.16 custom (sub-classed) theme issue

This is related to WW-4145, I think. When upgrading to 2.3.16, we're receiving the following error messages for our locally created theme. This theme builds off of the simple theme, but mostly includes "custom" controlheader and controlfooter elements. The issue we're seeing is that struts seems