Yes - it's not hard. Look in the Velocity source code for examples. Though
if you search the mailing list archives, I think someone already wrote one.
WILL
----- Original Message -----
From: "Robert Zeigler" <[EMAIL PROTECTED]>
To: "Velocity Users List" <[email protected]>
Sent: Thursday, August 04, 2005 2:51 PM
Subject: Re: "template" caching when using evaluate?
Thanks. Would a better alternative, then, to be to implement
some sort of custom resource loader?
Thanks again,
Robert
Will Glass-Husain wrote:
No. For frequent Velocity parsing, using evaluate can be a major
performance hit.
Best,
WILL
----- Original Message ----- From: "Robert Zeigler" <[EMAIL PROTECTED]>
To: "Velocity Users List" <[email protected]>
Sent: Thursday, August 04, 2005 2:22 PM
Subject: "template" caching when using evaluate?
Hello,
I'm in the process of integrating velocity into an app.
The templates are pulled from a database, so I'm using
the "evaluate" method, providing the templateTag, etc.
(assuming caching is enabled), does velocity attempt to
cache the inString text?
Thanks,
Robert
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
