You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Sauthier (JIRA)" <ji...@apache.org> on 2008/02/26 14:15:54 UTC
[jira] Closed: (FELIX-501) iPOJO Component should log detailed
error messages
[ https://issues.apache.org/jira/browse/FELIX-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Sauthier closed FELIX-501.
------------------------------------
> iPOJO Component should log detailed error messages
> --------------------------------------------------
>
> Key: FELIX-501
> URL: https://issues.apache.org/jira/browse/FELIX-501
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Reporter: Guillaume Sauthier
>
> I think it could be useful to have 2 things in iPOJO:
> * the container/component should log detailed error messages (including stack traces)
> * a way to configure traces level (I did not found how to configure that)
> Actually sometimes I get that kind of messages, that are a little useless without more data:
> [org.ow2.jonas.ejb.easybeans.EasyBeansService] ERROR: [org.ow2.jonas.ejb.easybeans.EasyBeansService.f6da84da-c53f-42c1-8d07-de229ce4e85c] The callback method start has throws an exception : org/xml/sax/EntityResolver
> Having the staack trace helps always a lot when developing :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.