topic Re: Authentication within a Job in Alfresco Archive

Authentication within a Job

hubick — Thu, 18 Apr 2013 21:04:26 GMT

Hi,I have an a org.quartz.Job subclass for creating folders within my repository (v3.3.5).I have been using only the JCR API up until recently, but now I also wish to populate content rules on the created folders, so I mixed in some native Alfresco API calls to create those.Despite having wrapped my

Re: Authentication within a Job

afaust — Fri, 19 Apr 2013 08:11:12 GMT

Hello,

why did you use JCR API in a job that runs in Alfresco? Just out of curiosity…

When you invoke Alfresco services from a Quarts job, you not only need to wrap your calls in a proper authentication context via runAs, but also in a proper transaction context (e.g. via RetryingTransactionHelper), which I see is lacking from your thread dump. Or is this contained in the part that you have snipped?

Regards
Axel

Re: Authentication within a Job

hubick — Fri, 19 Apr 2013 22:05:20 GMT

I had assumed 'ApplicationContextHelper.getApplicationContext().getBean(ServiceRegistry.SERVICE_REGISTRY)' would follow the singleton pattern, but it doesn't, and getApplicationContext() was instead causing the duplicate instance of Alfresco to be instantiated. Injecting the existing ServiceRegistry instance via a <ref bean="ServiceRegistry" /> solved the problem.

And coding projects against a standard interface such as the JCR API's when possible, as opposed to the proprietary Alfresco Foundation API's, attempts to avoid vendor lock-in - both in terms of the implementation runtime and the knowledge required to maintain the resulting code.

Regards.