Jason van Zyl wrote:
>
> On 6/27/01 10:22 AM, "Leandro Saad" <[EMAIL PROTECTED]> wrote:
>
> > Jason van Zyl wrote:
> >>
> >> Hi,
> >>
> >> Here's a summary of next round of changes coming into CVS.
> >>
> >> Again, the primary goal was to try and isolate the services so
> >> that they can be built as a separate entity. This is still not
> >> completely possible because all the services have not been
> >> separated.
> >>
> > I don't know for sure if this change because this commit,
> > but I know that services don't have early initialization anymore.
> > My question is, Does SchedulerService get started when we initialize
> > Turbine ??
>
> The services have early initialization, and it is controlled with
> a service property. For the scheduler you would have the following:
>
> services.SchedulerService.earlyInit = true
>
> And this will start the scheduler service when the service manager
> is initialized. Any service can be started early with the 'earlyInit'
> property.
>
> > or it relies on late initialization ??
>
> I'm actually not sure if the scheduler service works with late
> init. But you can definitely make sure it goes on when the
> system comes up by using the 'earlyInit' property.
>
Ok.
shouldn't the line in TR.props
-> services.SchedulerService.scheduler.enabled=true
be changed to
-> services.SchedulerService.earlyInit = true
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
