Hi, I've done some substantial changes to the Sling event bundle. I've moved all the code to the resource API, leveraging the CRUD stuff. While this lead to cleaner/simpler code, it also revealed some bugs/problems with the jcr resource bundle.
But the biggest change is leveraging the new discovery API which allows to know the instances in the topology, the capabilities of an instance and act on changes thereof. The discovery API also does a leader election, so there is one dedicated instance which can be used for things that really should only run on a single instance. I've updated all parts of the event bundle, job handling, timed job events and distributed events, to use this new feature. I've also looked at the configuration and reduced the metatype information to those settings which are really meant to be changed. So there are less options visibile in tools like the web console whle of course still the same set of configuration properties is supported. For example the resource path where jobs are stored is configurable but there is rarely a need to change this. Therefore no metatype information is generated for this anymore. But as said, the configuration is compatible to previous versions. And last but not least, I've also added a new API for starting a job and a new interface for processing the job. The old implementations leveraged the event admin for both parts which adds a little bit of uncertainty to creating and processing the jobs. With the new service based API we have more stable contracts. Of course the old way is still supported. Regards Carsten -- Carsten Ziegeler [email protected]
