On Tue, 07 Mar 2006 01:39:15 +0100, Will Glass-Husain <[EMAIL PROTECTED]>
wrote:
Sure, why not?
because then users who like to know if a subsystem is configured
before using it will not get a warning/exception.
I would rather say that all the static singleton functionallity
should be ripped out of velocity since it is a Bad Thing.
/max
On 3/6/06, Nathan Bubna <[EMAIL PROTECTED]> wrote:
hey guys,
here's another idea i've only half-thought through... :)
why do we require users to manually init() Velocity? are our default
settings that useless?
i know most users will still want and need to do init(props), so it
ultimately isn't a big deal either way. but i think it could be a
nice convenience to automatically call init() when someone tries to
use Velocity, especially for those using Velocity.evaluate(). as it
is, we (sometimes) throw IllegalStateExceptions if someone is trying
to use Velocity and RuntimeInstance.isInitialized() returns false.
why not just call init() instead of barking at the user?
feedback appreciated. :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
_______________________________________
Forio Business Simulations
Will Glass-Husain
phone (415) 440-7500 x89
mobile (415) 235-4293
[EMAIL PROTECTED]
www.forio.com
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
