John McNally wrote:
>
> I also have been in need of something like this. In my case the class does
> not need RunData to initialize and I would prefer that it be init'ed when
> Turbine is loaded. This way I can specify Turbine to be loaded at startup
> and the class will be available as soon as Apache/JServ are running.
Yes. I agree. I thought about this before my proposal and I was
probably being selfish by not recommending it. This is a significant
advantage if you don't need RunData.
The RunData issue is my problem. When Cocoon 2.0 ships this won't be an
issue any more. But this is still 6 months away :(
How about this:
turbine.init.classname=<CLASSNAME>
turbine.init.onstartup=<BOOLEAN>
If the user specifies onstartup=true then we can call this from init()
and if false we will call it from doGet()
Thoughts?
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
I just patented "one click e-mail", when you hit the "reply" button you
own me 50 cents.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
