You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Dieter Wimberger (JIRA)" <ji...@apache.org> on 2008/06/01 07:10:45 UTC
[jira] Created: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: FELIX-585
URL: https://issues.apache.org/jira/browse/FELIX-585
Project: Felix
Issue Type: Bug
Reporter: Dieter Wimberger
Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
java.lang.IllegalArgumentException: Object Class Definition ID not found
The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
Example:
When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dieter Wimberger updated FELIX-585:
-----------------------------------
Component/s: Web Console
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned FELIX-585:
---------------------------------------
Assignee: Felix Meschberger
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Assignee: Felix Meschberger
> Fix For: webconsole-1.0.2
>
> Attachments: ConfigManager.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-585:
------------------------------------
Fix Version/s: webconsole-1.0.2
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Fix For: webconsole-1.0.2
>
> Attachments: ConfigManager.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dieter Wimberger updated FELIX-585:
-----------------------------------
Attachment: ConfigManager.java.diff
I think it should have been this one.
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Attachments: ConfigManager.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604812#action_12604812 ]
Felix Meschberger commented on FELIX-585:
-----------------------------------------
Isn't this (almost) the same as FELIX-586 ? At least the patch seems to be the same...
With my patch [1] attached to FELIX-587, this issue should also be solved as for a configuration with factory PID only the factory PID would be considered.
WDYT ?
[1] https://issues.apache.org/jira/secure/attachment/12383956/FELIX-587-fmeschbe.patch
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Attachments: ConfigManagerBase.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dieter Wimberger closed FELIX-585.
----------------------------------
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Attachments: ConfigManager.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604971#action_12604971 ]
Dieter Wimberger commented on FELIX-585:
----------------------------------------
Looks to me as if I messed up the patches.
I will take a look at your updates and check if it fixes the problem.
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Attachments: ConfigManagerBase.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dieter Wimberger updated FELIX-585:
-----------------------------------
Attachment: ConfigManagerBase.java.diff
This patch includes the fix for FELIX-583.
Obtained using:
svn diff ConfigManager.java > ConfigManager.java.diff
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Attachments: ConfigManagerBase.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dieter Wimberger updated FELIX-585:
-----------------------------------
Attachment: (was: ConfigManagerBase.java.diff)
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-585)
org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
Configuration instances for ManagedServiceFactoy instances cause
IllegalArgumentException
Posted by "Dieter Wimberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dieter Wimberger resolved FELIX-585.
------------------------------------
Resolution: Fixed
The updated version of the webconsole takes a different approach, which resolves this issue.
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations(): Configuration instances for ManagedServiceFactoy instances cause IllegalArgumentException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-585
> URL: https://issues.apache.org/jira/browse/FELIX-585
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Dieter Wimberger
> Attachments: ConfigManager.java.diff
>
>
> Once a Configuration can be created for a ManagedServiceFactory instance, this instance will cause a IllegalArgumentException in
> org.apache.felix.webconsole.internal.compendium.ConfigManager.listConfigurations():
> java.lang.IllegalArgumentException: Object Class Definition ID not found
> The reason for this is the fact that the code does not properly look for the ObjectClassDefinition of the factory (which would apply in the case of ManagedServiceFactory instances).
> Example:
> When creating a Configuration instance for the factory "net.wimpi.telnetd.service.TelnetListenerServiceFactory", the ConfigurationAdmin will assign a unique identifier (pid) for the Configuration instance e.g. "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7". This Configuration has the pid "net.wimpi.telnetd.service.TelnetListenerServiceFactory-1212198114040-7", but there will never be any ObjectClassDefinition for this pid available from the MetaTypeService.
> Given that the code does not check for an associated factoryPid FIRST, the exception will happen and nothing will appear in the list in the console form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.