You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Pierre De Rop (JIRA)" <ji...@apache.org> on 2016/02/27 19:04:18 UTC
[jira] [Created] (FELIX-5201) Improve how
Pierre De Rop created FELIX-5201:
------------------------------------
Summary: Improve how
Key: FELIX-5201
URL: https://issues.apache.org/jira/browse/FELIX-5201
Project: Felix
Issue Type: Improvement
Components: Dependency Manager
Affects Versions: dependencymanager-3.2.0
Reporter: Pierre De Rop
Assignee: Pierre De Rop
Priority: Minor
Fix For: org.apache.felix.dependencymanager-r7
When listing DM components with the gogo DM shell, components which are instantiated using a factory with Component.setFactory(...) method are displayed using the DM internal ComponentImpl class name.
For example:
{code}
[0] org.apache.felix.dm.impl.ComponentImpl@3891771e registered
org.osgi.service.cm.ConfigurationAdmin service required available
{code}
Now when a factory object is used as the component definition, it's not good to use the ComponentImpl classname as the component name and display it from gogo shell.
Instead, the factory object instance itself should be displayed (or the component instance if it is already instantiated by the factory).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)