Mirko Buholzer wrote:
>
> I have the same problem on my machine.
>
> > The reason, as I have tracked, is that FeedDaemon starts running before
> > RegistryManager is fully initialized. I managed to solve this, but now
> > the problem is that FeedDaemon starts producing feed before the
> > PortletRegistry gets initialized.
>
> Shoulden't there be a service dependency in the configuration file? So the
> Services are started with certain constraints like the Windows NT Services do.
>
> services.[service name].dependOnService.RegistryManager
> services.[service name].dependOnService.PortletCache
>
> Every service must inform the service factory when he is up and running. So
> the factory can start up dependent services.
>
The dependency mechanism already exists in Turbine services and you don't even
have to specify them manually.
I don't see how the feed dameon can use the registry before it is initialized, when
it tries to get a handle to the service through the static accessor class, the
service framework kicks in and makes sure the service is initialized before
handing back a reference to the singleton.
Looking at the init code of the service, all the registries are loaded synchronously
in the init method so either there's a bug in the Service framework or
the interaction bug is more subtle between FeedDaemon and RegistryManager.
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
