Thanks, Stefan. I did wind up getting things working with getServiceResourceResolver(); setting up the service user mapping turned out to be quite easy.
For the background work I'm just using the Sling ThreadPoolManager service to make a thread pool for now, though I had looked at [1] and the job support may be useful later. John On Monday, March 20, 2017 1:23 AM, Stefan Seifert <[email protected]> wrote: > > for background jobs you should have a look at [1]. > > if you have code running in the background without a requrest you > have to create a resourceresolver instance yourself, and close it > when you're done. > > you should always use getServiceResourceResolver. [snip] > [1] > https://sling.apache.org/documentation/bundles/apache-sling-eventing-and-job-handling.html
