[
https://issues.apache.org/jira/browse/FELIX-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295162#comment-15295162
]
David Jencks commented on FELIX-4178:
-------------------------------------
The spec generally requires us to log problems, so that's not going away, and
seems to be the official way to indicate something is wrong. I don't
understand how presenting this information in an additional way can be
considered anything except duplication. Also, since your proposal seems to me
to be based on querying status I don't see how it would relate to an alert in
a management system, which I associate with a pushed event, such as from a log
reader. You also seem to be changing your story about what you want to listen
for: the original proposal indicated situations that could only be fixed by
code or packaging changes, and now you seem to have something else in mind.
> 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)
