[
https://issues.apache.org/jira/browse/FELIX-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767382#comment-13767382
]
Christoph Läubrich commented on FELIX-4179:
-------------------------------------------
Hi [~djencks] can you explain what has changed? And when 1.8 will be released?
My point is not that the component might not activate properly later, it is
just hat currently (with 1.6) there is no way to know it has failed AT THE
MOMMENT, because it is just reported as UNSATISFIED what is confusing since all
references are satisfied, but the activator failed.
e.g. Equinox let those components reside in the ACTIVATING state and reports
back the exception in its 'comp' command.
What I want to archive is an automatic diagnostic tool that tells me whenever
something is wrong at the current time, at the mommernt I try to guess this by
check if all components are satisfied, but the same state can occur when the
configuration policy is require so its a little ugly to guess whats wrong, an
explicit state, or a "activation exception" would help alot.
> SCRService should provide state "FAILED" for failing components
> ---------------------------------------------------------------
>
> Key: FELIX-4179
> URL: https://issues.apache.org/jira/browse/FELIX-4179
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Reporter: Christoph Läubrich
> Assignee: David Jencks
> Fix For: scr-1.8.0
>
>
> At the momment the state "UNSATISFIED" is reported for component throwing an
> exception in the activate method. This is confusing since in fact all
> references/configurations are satisfied. It would be better to report this
> problem with a state of "FAILED"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
