Raphael, I built Jetspeed from CVS head this morning and the problems I noticed before are gone. The registry load performance is better than ever! I noticed one thing though: there are duplicate entries created in the registries after they are auto-saved. The app appears to work normal and the browsers do not show any duplicate entries. However, if you examine one of the registries (demo_portles.xreg, for example), you'll notice that AggregatePortlet, BBCTechnology, InstanceExample + more are listed twice. There are no duplicates in registries contained in the .war file so this must be happening after they are auto-saved.
It seems that the RegistryWatcher saves all the registries immediately after the app has started. Is that an intended behaviour? It would be nice to have an option to disable the auto-save (or is it achieved via services.Registry.refreshRate=0?) but still have the auto-load-when-changed-on-disk capability. Best regards, Mark C. Orciuch Next Generation Solutions, Ltd. e-Mail: [EMAIL PROTECTED] web: http://www.ngsltd.com > -----Original Message----- > From: Luta, Raphael (VUN) [mailto:Raphael.Luta@;groupvu.Com] > Sent: Saturday, November 02, 2002 8:14 AM > To: 'Jetspeed Developers List' > Subject: RE: Strange registry service behaviour > > > De : Mark Orciuch [mailto:mark_orciuch@;ngsltd.com] > > > > <snip> > > [31 Oct 2002 13:43:25 DEBUG] - Adding entry XML of class class > > org.apache.jetspeed.om.registry.base.BasePortletEntry to > > registry Registry > > [31 Oct 2002 13:43:27 ERROR] - Could not unmarshal: > > C:\jakarta-tomcat\webapps\jetspeed\WEB-INF\conf\portlets.xreg > > org.xml.sax.SAXParseException: XML document structures must > > start and end > > within the same entity. > > I noticed this one also, even before committing my changes, I > think there's > a > corruption in the portlets.xreg file... I'll try to hunt it down. > > > > > Also, the registry seems to refresh itself at > > services.Registry.refreshRate > > even if NOT changed: > > > > For some reason, I thought that refresh was only triggered by file > > modification. > > > > It's supposed to be refreshed only on modification but I think > this bug was > created quite some times ago... > > > I'll look into it further but I would appreciate any other > > comments. Many > > thanks in advance! > > > > I'll check the registry "slow" behavior to check if ot's somewhat > related to > a change > I made. > > -- > To unsubscribe, e-mail: <mailto:jetspeed-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:jetspeed-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-dev-help@;jakarta.apache.org>
