[
http://jira.nuxeo.org/browse/WEB-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48175#action_48175
]
Florent Guillaume commented on WEB-155:
---------------------------------------
We already have a collector for for bundle errors are startup, they are
collected and printed like:
19:50:47,888 ERROR [OSGiRuntimeService] Nuxeo EP Started
======================================================================
= Nuxeo EP Started
======================================================================
= Component Loading Errors:
* Duplicate component name: 'service:org.nuxeo.ecm.webengine.config'
======================================================================
= Component Loading Status: Pending: 0 / Unstarted: 0 / Total: 222
======================================================================
In addition to duplicate components, you can also see here other kinds of
errors related to bundle loading. Why not expand this with further errors if
applicable?
> improve debugging capabilities for osgi bundles
> -----------------------------------------------
>
> Key: WEB-155
> URL: http://jira.nuxeo.org/browse/WEB-155
> Project: Nuxeo Web Engine
> Issue Type: Improvement
> Reporter: Ian Smith
> Assignee: Ian Smith
>
> The problem: When you are developing your own code based on nuxeo EP or
> webengine it is easy to make a mistake and then your code will mysteriously
> "disappear" from the system. This is because the OSGi bundle was considered
> invalid in some way.
> Solution: Add a debugging channel (log4j logger) that is only for this type
> of information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
