[
https://issues.apache.org/jira/browse/ARIES-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871943#action_12871943
]
Alasdair Nottingham commented on ARIES-323:
-------------------------------------------
I guess I shouldn't quickly write one of these up as just before I go home :)
When I used the word event I was thinking of more of a System.out call (well
not literally, but a log message that gets written to System.out).
Having used blueprint for a while I have never seen anything sent to System.out
that reports the entry into the wait state/grace period. I have seen the expiry
noted though. I was hoping of some way to get something similar for the entry.
That way developers don't need to write any code to work out their
blueprint.xml has a reference created incorrectly.
Looking at the BlueprintEventDispatcher the event is debugged, so it wont
become visible to a developer unless they enable debug trace. In this case I
would like to promote this case to a warning.
Alasdair
> Emit an event/warning when a blueprint cannot find its services and moves
> into the wait state
> ---------------------------------------------------------------------------------------------
>
> Key: ARIES-323
> URL: https://issues.apache.org/jira/browse/ARIES-323
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: 0.1
> Reporter: Alasdair Nottingham
>
> If a mandatory dependency is not available the bundle goes into a wait state
> waiting up to n minutes (where n is 5 by default) for the dependencies to
> become available. This means if a mistake is made the user has to wait 5
> minutes to get any indication of a problem. It would be really good if we
> could emit an event, somehow, that indicated that the bundle was in this wait
> state when entered to reduce this time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
