OSGi eventing by itself has no priority - the Sling job handling doesn't have this either. The JobPriority you're referring to, is just used to set the priority of the thread executing the job. But it doesn't contol when this thread will be started.
But you could put your A and B jobs into different job queues - configure one for each - if you then configure the priority for the B queue to MAX, B jobs are performed with a higher priority than A tasks. However this gives you only minimum control and does not ensure that A jobs are processed before a new B job. Regards Carsten 2012/8/10 Robert A. Decker <[email protected]>: > Hi, > > EventUtil.JobPriority is deprecated. Reading the docs I'm not sure how I'd > use it anyway, unless it's just used automatically be the osgi eventing > system. > > Since it's deprecated is there another way to set job priorities? > > I have a situation where event type A fires off high-priority event types B > that should preferably be processed before any other already existing event > type A are processed. > > Rob -- Carsten Ziegeler [email protected]
