There's a couple of options here.
One is to use a common base class that defines all of these getters.
Create your own component that acts like an If but the tests is hard
coded against the
getUsesSetting() logic.
Another option is to create a new binding prefix, i.e.,
Where the uses: prefix
I knew this felt familiar; the issue came up a couple months ago, but
with no solution at the time. This isn't a really a problem, it's a
matter of convenience for programmers.
The thread was:
"T5: static page variables in templates"
On 10/9/07, Daniel Jue <[EMAIL PROTECTED]> wrote:
> Hi, I want
Hi, I wanted to try eliminating a bunch of getters in my Java class.
Right now I have something like this in my template:
And I have a getter that is
public boolean getShowYear() {
return this.getUsesSetting(ReportVariableEnum.FISCALYEARSINGLE);
}
I want to do something lik
