[
https://issues.apache.org/jira/browse/FELIX-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925290#action_12925290
]
Felix Meschberger commented on FELIX-2671:
------------------------------------------
104 [RFC 160/Coordinator Service] Coordinator Life Cycle
Fixed in Rev. 1027833 by really failing active Coordinations when the service
is ungotten.
> Apply changes from feedback to Coordinator Service draft (RFC160)
> -----------------------------------------------------------------
>
> Key: FELIX-2671
> URL: https://issues.apache.org/jira/browse/FELIX-2671
> Project: Felix
> Issue Type: Task
> Components: Coordinator Service, Specification compliance
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> After a first implementation and reading the draft 3 spec I have reported a
> number of bugs with the OSGi bug database:
> 95 [RFC 160/Coordinator Service] Reentrant Participant
> 96 [RFC 160/Coordinator Service] Coordination Nesting
> 97 [RFC 160/Coordinator Service] Clarification on Coordination.end
> 98 [RFC 160/Coordinator Service] Undocumented Coordination.getVariable
> method
> 99 [RFC 160/Coordinator Service] Forcing Coordination active on a single
> thread
> 100 [RFC 160/Coordinator Service] Undocumented Coordinator.isActive method
> 101 [RFC 160/Coordinator Service] Wrong value for TIMEOUT constant
> 102 [RFC 160/Coordinator Service] Wrong type for COORDINATIONS_TYPE constant
> 103 [RFC 160/Coordinator Service] JavaDoc of Coordination.end()
> 104 [RFC 160/Coordinator Service] Coordinator Life Cycle
> 105 [RFC 160/Coordinator Service] Missing CoordinationException on
> Coordinator.participateOrBegin
> This issue is to track required changes as a consequence of the resolution
> these bugs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
