Hi, Am Freitag, den 13.06.2008, 15:15 -0700 schrieb Dieter Wimberger (JIRA): > There is a corresponding metatype description. > > The way you approached to fix the chain of issues I reported (sorry for the > messed up patch), it occurs difficult to me to track them properly. Also, I > have a question for you: > Do you actually have a test case? If yes, which one is it?
I now tested my last patches against Equinox MetaType and Configuration Admin service implementations and found out that Equinox Configuration Admin does not persist created factory configurations until first updated whereas the Apache Felix implementation immediately persists such created configurations. So, now the configuration is correctly displayed by the configuration admin... Regards Felix > > Regards, > Dieter > > > > > > org.apache.felix.webconsole.internal.compendium.AjaxConfigManagerAction.configForm(): > > Configuration instance for a ManagedServiceFactory will cause Exception > > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Key: FELIX-587 > > URL: https://issues.apache.org/jira/browse/FELIX-587 > > Project: Felix > > Issue Type: Bug > > Components: Web Console > > Reporter: Dieter Wimberger > > Attachments: AjaxConfigManagerAction.java.diff, > > FELIX-587-fmeschbe.patch > > > > > > A Configuration instance for a ManagedServiceFactory will cause an > > Exception in > > org.apache.felix.webconsole.internal.compendium.AjaxConfigManagerAction.configForm(), > > because the implementation will try to obtain an ObjectClassDefinition for > > the Configuration pid, rather than for the corresponding factoryPid. > > Fix: > > The method should verify if a factoryPid is assigned to the Configuration > > instance and handle this case properly. >
