felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3692) [DS] api for finding out if async work is done
Date Sun, 30 Sep 2012 01:10:07 GMT

     [ https://issues.apache.org/jira/browse/FELIX-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Jencks updated FELIX-3692:

    Attachment: FELIX-3692-1.diff

Simple api to determine if async work is completed.  This is slightly entangled with the 2nd
"later" patch to FELIX-3557, that will be needed to apply this one cleanly.
> [DS] api for finding out if async work is done
> ----------------------------------------------
>                 Key: FELIX-3692
>                 URL: https://issues.apache.org/jira/browse/FELIX-3692
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.8.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.8.0
>         Attachments: FELIX-3692-1.diff
> It might be useful to provide a couple methods on ScrService so you can find out if all
the async work is done.
> I'm thinking
> boolean tasksCompleted()
> void waitForTasksCompleted()
> This might be especially useful if we decide to adopt my "try again later" proposal for
resolving more circular dependencies (FELIX-3557) since that can result in extra possibly
unexpected async tasks.

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

View raw message