Nathan Bubna wrote:
On Mon, Dec 29, 2008 at 10:21 AM, Steve Cohen <[email protected]> wrote:
...
Maybe, as you say, I am
developing an application which doesn't need to play with anyone else and
just can't see the need, therefore, have no such need. Are you saying
that, at some point in the future I may uncover a need for a totally
different use of Velocity within my application, requiring different init
parameters?
yep. but most people don't.
At that point, I suppose I could write another wrapper for this
other set of client code (static as well, perhaps) and the two could live in
blissful ignorance of each other.
yep, so long as both are not trying to use the singleton under the covers
No, I made my singleton out of my wrapper class, whose single instance
wraps one VelocityEngine, not Velocity. Any other future wrappers would
follow the same pattern, so we should be okay in that event too.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
