Managing Queues based on Topology ?

Hi, (Probably a question for Carsten). Is the right way to implement topology based queue exclusion by implementing a topology discovery PropertyProvider that provides the property: org.apache.sling.event.jobs.consumer.topics containing a , separated list of topics the instance can handle. If

Re: Managing Queues based on Topology ?

Hi Ian, no, you don't implement a PropertyProvider for this - this is done by the job implementation for you (JobConsumerManager). The JobConsumerManager collects all active JobConsumer queries their supported topics and provides this information through the topology by registering the

Re: Managing Queues based on Topology ?

Cool, thanks, I'll go down the route you suggest. Ian On 6 September 2013 11:45, Carsten Ziegeler cziege...@apache.org wrote: Hi Ian, no, you don't implement a PropertyProvider for this - this is done by the job implementation for you (JobConsumerManager). The JobConsumerManager collects all

Re: Managing Queues based on Topology ?

Hi, Just to be clear you are saying programatically manipulate the OSGi configuration of the JobConsumerManager when an instance initialises or transitions from master-slave ? eg on a topology change get a serviceReference to the JobConsumerManager using

Re: Managing Queues based on Topology ?

I meant serviceRegistration not serviceReference, but I cant get it seems like its not possible to get hold of a serviceRegistration from another bundle. On 6 September 2013 13:31, Ian Boston i...@tfd.co.uk wrote: Hi, Just to be clear you are saying programatically manipulate the OSGi

Re: Managing Queues based on Topology ?

If the config is stored in the repository, wont that propagate from master to slave and visa versa ? The JavaDocs on Configuration.update(Dictionary) say changes are stored. On 6 September 2013 13:40, Carsten Ziegeler cziege...@apache.org wrote: Hmm, I would rather get the configuration

Re: Managing Queues based on Topology ?

In general yes, but not for the Job Consumer Manager - the configuration has a special property set which excludes it from writing back to the repository and therefore distributing it Carsten 2013/9/6 Ian Boston i...@tfd.co.uk If the config is stored in the repository, wont that propagate

Re: Managing Queues based on Topology ?

Sorry, not slightly correct - if you create the configuration for the first time, make sure to set the property org.apache.sling.installer.configuration.persist to the value false Carsten 2013/9/6 Carsten Ziegeler cziege...@apache.org In general yes, but not for the Job Consumer Manager - the