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.
----- Original Message -----
From: Jon Stevens <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Wednesday, May 24, 2000 3:08 PM
Subject: Re: (PROPOSAL) Initializing external code within Turbine.
> on 5/24/2000 1:17 PM, Kevin A. Burton at [EMAIL PROTECTED] wrote:
>
> > Thoughts?
>
> I am 100% behind the need for this.
>
> I'm not 100% on your proposal for implementation (more like 90%). I want
to
> make sure that we do this right the first time and catch all the cases.
So,
> I will want to talk about it a bit before implementation. Is that ok?
>
> What I would like is the ability to somehow "register" classes that need
to
> be initialized and then go through each of those classes and initialize
> them. You have covered this with your proposal. What you have not covered
is
> the methodology to do all of the registration of the initializations. It
can
> be as simple as properties in a properties file. Do we need to consider
that
> some things might need to be registered before other things?
>
> Also, you are passing in a RunData object in
TurbineInitable.init()...since
> that really won't be available at this point in time, I think it would be
> better to essentially extend the Servlet API HttpServlet.init() method and
> pass in a ServletConfig object instead...
>
> -jon
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
