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

Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/06/25 11:03:42 UTC

[jira] [Created] (SLING-2519) Use Sling scheduling in the Slingbucks sample ConfirmerOdersObserver class

Bertrand Delacretaz created SLING-2519:
------------------------------------------

             Summary: Use Sling scheduling in the Slingbucks sample ConfirmerOdersObserver class
                 Key: SLING-2519
                 URL: https://issues.apache.org/jira/browse/SLING-2519
             Project: Sling
          Issue Type: Bug
            Reporter: Bertrand Delacretaz


That class currently starts a thread using itself as the Runnable, which can be a bit confusing.

Also, it doesn't stop the thread if deactivated, which is not good.

Switching to Sling scheduling will makes things simpler and more robust.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2519) Use Sling scheduling in the Slingbucks sample ConfirmerOdersObserver class

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.

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

Bertrand Delacretaz resolved SLING-2519.
----------------------------------------

    Resolution: Fixed

Fixed in revision 1353440
                
> Use Sling scheduling in the Slingbucks sample ConfirmerOdersObserver class
> --------------------------------------------------------------------------
>
>                 Key: SLING-2519
>                 URL: https://issues.apache.org/jira/browse/SLING-2519
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Bertrand Delacretaz
>
> That class currently starts a thread using itself as the Runnable, which can be a bit confusing.
> Also, it doesn't stop the thread if deactivated, which is not good.
> Switching to Sling scheduling will makes things simpler and more robust.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira