Jon Stevens wrote:
>
> on 5/26/2000 3:48 PM, burtonator at [EMAIL PROTECTED] wrote:
>
> > So if there are no -1s that this is a kludge I will do this.
>
> -1 because:
>
> > > turbine.external.init.classname=<CLASSNAME>
> > > turbine.external.init.onstartup=<BOOLEAN>
>
> this assumes that everything will be loaded on startup or not on startup.
> this should be defined on a class by class basis.
Fine. Actually it would be nice to have init() and init(RunData)
called. This way you can do base initialization and RunData
initialization and maximize both situations :)
> also, we *could* add load ordering by doing something like this:
>
> turbine.external.init.1.classname
> turbine.external.init.2.classname
This is fine. Actually it works out better because both scenarios
work. You could do single initialization by just using init.1 or
multiple if you wanted. I personally think it is a bad idea to do your
initialization that way but this is 50/50 and should be up to the
developer.
> > /**
> > Called on Turbine.init()
> > */
> > public void init()
>
> it should be void init(ServletConfig config)
Oops. +1
Hopefully I will have an impl of this tonight.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
