[
http://jira.nuxeo.org/browse/WEB-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48169#action_48169
]
Ian Smith commented on WEB-155:
-------------------------------
Imported from the dev mailing list:
The objective is to prevent the "silent failure" problem when developing
your own bundles. To do this I created a new log channel that is OFF by
default and is not inherited by any other log channel so it should have
no effect on those who don't need or want it.
Here is the proposed log4j snippet if you want to turn on debugging OSGi
bundle loading and other startup information:
log4j.logger.nuxeo.bundle.debug=DEBUG
Again, normally this should be off. However, if you turn this on, you
get a huge amount of information because nuxeo bundles themselves are
included in the output. So, I allowed the person doing the debugging to
filter how much they wanted to see by using log levels. This seemed
easier than trying to create even more new channels... here is the info:
log4j.logger.nuxeo.bundle.debug=INFO --- this shows you the OSGi bundle
loading info for alll packages that are not part of "org.nuxeo"
log4j.logger.nuxeo.bundle.debug=WARN --- this shows you JUST the
information about what webengine is doing as it is starting up ... (e.g.
what config files is it using, which is it ignoring)
I thought this (bad) use of WARN was ok since 1) it is off by default
and 2) only used by developers for a specific task. I guess I was
wrong, since two people have said this was bad form. :-(
> 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
