You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/03/25 16:28:20 UTC

[jira] [Commented] (OAK-1603) Operations tasks api improvements

    [ https://issues.apache.org/jira/browse/OAK-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946672#comment-13946672 ] 

Carsten Ziegeler commented on OAK-1603:
---------------------------------------

[~mduerig] Lgtm, thanks

> Operations tasks api improvements
> ---------------------------------
>
>                 Key: OAK-1603
>                 URL: https://issues.apache.org/jira/browse/OAK-1603
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.19
>            Reporter: Carsten Ziegeler
>            Assignee: Michael Dürig
>             Fix For: 0.20
>
>         Attachments: OAK-1603.patch
>
>
> The mbean approach added with OAK-1160 only allows to start an operation and gets its status as a string.
> There is no programatical way to find out, whether such an operation is currently running, if the start is really successful, and when the operation is finished.
> The only way currently to achieve this is doing string parsing and knowing internals of how the string is created for each operation.
> It would be nice to have such methods like isRunning() or isFinished() etc.



--
This message was sent by Atlassian JIRA
(v6.2#6252)