I have my screen templates set up like this:
.../templates/screens
.../templates/screens/account
.../templates/screens/news
.../templates/screens/reports
In my TR.props file I specify the following:
services.VelocityService.file.resource.loader.path = /templates
services.VelocityService.file.resource.loader.path = /templates/screens
services.VelocityService.file.resource.loader.path = /templates/screens/account
services.VelocityService.file.resource.loader.path = /templates/screens/news
etc
Now, in my action and screen classes I can specify a template like this:
data.setScreenTemplate("CreateAccount.vm")
without regard of where it is physically. I do not want to say:
data.setScreenTemplate("account,CreateAccount.vm")
In order to get this to work. I needed to remove the hard coding
of "screens" being prepended to my template names. In
in a couple of files (for velocity)
VelocityScreen.java
TurbineTemplateService.java
Does anyone else want this desired behavior? I like it.
Both my templates and my classes no longer need to specify a prefix
(unless there's ambiguity)
Why not let the search paths be configurable via props? As usual,
I may be missing something obvious which allows me to do what I want
but I can't figure it out :). Let me know.
mike
--
-------------------------------------------------
I am Vinz, Vinz Clortho. Keymaster of Gozer,
Volguus Zildrohar, Lord of the Sebouillia.
Are you the Gatekeeper?
-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
