felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-501) iPOJO Component should log detailed error messages
Date Tue, 26 Feb 2008 12:47:51 GMT

    [ https://issues.apache.org/jira/browse/FELIX-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572459#action_12572459
] 

Clement Escoffier commented on FELIX-501:
-----------------------------------------

Hi,

I agree with these improvements (it is already implemented :-)).
In the sandboxed version, bundle can specify its own trace level. By the way, all component
types contained in the bundle will use this log level. The stack trace was added in message
too (more specially when an InvocationTargetExeption is thrown)

The merge is planned for the end of the week (I hope so).


> 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.


Mime
View raw message