on 12/6/2000 12:43 PM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
> Hey Magnus, this is not the proper way of solving the problem. I think
> that it's the services that are misbehaving. When a service
> calls setInit(true), no further initialization attempts will be made
> (check BaseInitableBroker.java, lines 150 & 210). Some services
> need both early and late initialization, therefore setInit(true) can
> not be called in early initalization routines. Another flag can be
> used by such service, to safeguard against double initialization.
>
> Tell me which services are giving you trouble, and I can fix them.
>
> Rafal
Ug. You are right. I'm going to back out that code from Turbine.java. I have
a feeling that the problem service is the Scheduler service because it was
init'd twice...once in Turbine.java and once within itself.
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
