On 12/14/06, David Elliot <[EMAIL PROTECTED]> wrote:
Hi Claude,
Thank you very much, using template = super.getTemplate("x.vm") fixes
the problem (my custom resource loaders from velocity.properties work
for the VVS... hurrah!).
Can you point me towards some documentation regarding why:
template = Velocity.getTemplate("x.vm");
Is bad ?? It's a nasty trap for the newbies!!!
well, to be precise, it's not necessarily bad if you have explicitly
initialized the Velocity singleton with your velocity.properties. if
you have not, then as of Velocity 1.5, it will assume you know what
you are doing and just auto-initialize with the default properties.
as for the particular fix here, i would actually recommend just doing
getTemplate(...)
instead of
super.getVelocityEngine().getTemplate(...)
in actuality these are doing the exact same thing right now. but the
latter will not be as future-proof against later changes to the
VelocityViewServlet.
On 12/14/06, Claude Brisson <[EMAIL PROTECTED]> wrote:
> That's probably the reason...
>
> template = super.getTemplate("x.vm") should be appropriate.
>
> Claude
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
