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

Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2020/09/14 10:49:00 UTC

[jira] [Created] (SLING-9730) Scheduler job mapping doesn't work correctly for lambdas.

Karl Pauls created SLING-9730:
---------------------------------

             Summary: Scheduler job mapping doesn't work correctly for lambdas.
                 Key: SLING-9730
                 URL: https://issues.apache.org/jira/browse/SLING-9730
             Project: Sling
          Issue Type: Bug
          Components: Commons
    Affects Versions: Commons Scheduler 2.7.6
            Reporter: Karl Pauls
            Assignee: Karl Pauls
             Fix For: Commons Scheduler 2.7.8


When scheduling a job that is a Runnable the mapping from job to instance is done based on the class name. That is problematic in case of lambdas as the class name is not stable. We should use a key that is stable for all cases. 

As we only have the object itself and the mapping needs to be stable across JVMs, the easiest mapping key seems to be the package name. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)