Raphaël Luta escribió:
>
> 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.
They are loaded, but not refreshed. I get the following errors:
[Thu Jan 25 10:54:11 GMT+01:00 2001] -- NOTICE -- BEGIN:
EntryInstantiator: Instantiating 5 Portlet(s) found in a Feed
[Thu Jan 25 10:54:11 GMT+01:00 2001] -- ERROR -- Null
PortletRegistry
Printed from:
EntryFactory.java
/**
This method might become obsolete in the future
*/
public static PortletEntry getEntry(
org.apache.jetspeed.xml.api.registrymarkup.Entry real ) {
//go through the registrymarkup capability-map and pull out the
//mime-types
PortletEntry entry = new PortletEntry();
entry.setName( real.getName() );
PortletRegistry registry = (PortletRegistry)RegistryManager
.get(RegistryManager.PORTLET_REGISTRY);
if( registry == null ) {
//Warning to diagnose problem
Log.error( "Null PortletRegistry" );
}
...
This is after some changes I did to avoid previous errors.
There is another error: when the FeedManager runs the second (and
successive) time, it spoils dynamic entries, with an error
"Entry did'nt have the classname set"
I have not been able to trace this one. Everything looks allright, but
it fails.
I am getting crazy trying to get rid of those problems, because I don't
understand how they are generated. Can you have a look to
them?
>
> --
> 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]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
