[
https://issues.apache.org/jira/browse/FELIX-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295308#comment-15295308
]
Simon Chemouil commented on FELIX-4178:
---------------------------------------
I would find this feature useful as well. I also don't think Christoph is
changing his story.
It makes sense for Apache Felix SCR to expose an API to have a
status/diagnostic UI, and to discover why components failed (and get the thrown
exception). This shouldn't be much of a memory issue if only the last exception
is kept (in case of bundle or prototype components), and I'm sure there are
smarter ways to design this.
While exceptions are already logged through the log service, it is not
practical/future-proof to parse log messages to find those that correspond to
exceptions thrown during the activate method.
> Provide method to access Exception thrown by activate method and/or while
> instantiation
> ---------------------------------------------------------------------------------------
>
> Key: FELIX-4178
> URL: https://issues.apache.org/jira/browse/FELIX-4178
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Reporter: Christoph Läubrich
> Assignee: David Jencks
>
> Access to the exception a component throws in the activate method or any
> exception while try to create instance (e.g. no default constructer, class
> not found...) would help for diagnostic tools depending on the ScrService.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
