Re: CommitHooks as OSGi Components.

2016-09-14 Thread Chetan Mehrotra
On Thu, Sep 15, 2016 at 1:15 AM, Rob Ryan wrote: > Last I heard even local events can be subject to loss of the user id if so > many events are being processed that ‘compaction’ is used to mitigate the > load. Is this still the case? > > Please don’t point people toward the

Re: CommitHooks as OSGi Components.

2016-09-14 Thread Rob Ryan
Last I heard even local events can be subject to loss of the user id if so many events are being processed that ‘compaction’ is used to mitigate the load. Is this still the case? Please don’t point people toward the availability of the user id from events (without full disclaimers) if it will

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Ian Boston
On 12 September 2016 at 10:45, Chetan Mehrotra wrote: > On Mon, Sep 12, 2016 at 3:12 PM, Ian Boston wrote: > > but if the information that connect a sessionID/userID to the > > paths that are modified is available through some other route, I might be >

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Chetan Mehrotra
On Mon, Sep 12, 2016 at 3:12 PM, Ian Boston wrote: > but if the information that connect a sessionID/userID to the > paths that are modified is available through some other route, I might be > able to use something else. A regular Observer should work for that case. Just register

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Ian Boston
Hi, On 12 September 2016 at 09:43, Chetan Mehrotra wrote: > On Mon, Sep 12, 2016 at 2:08 PM, Ian Boston wrote: > > Unfortunately the IndexProvider route doesn't appear give me the > > information I am after (CommitInfo). > > Any details around

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Chetan Mehrotra
On Mon, Sep 12, 2016 at 2:08 PM, Ian Boston wrote: > Unfortunately the IndexProvider route doesn't appear give me the > information I am after (CommitInfo). Any details around intended usage? CommitInfo is now exposed via OAK-4642 to IndexEditorProvider Chetan Mehrotra

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Ian Boston
Hi, Thank you for the pointers. Unfortunately the IndexProvider route doesn't appear give me the information I am after (CommitInfo). Since I need this to work in an independent bundle patching the repository manager isn't an option. I am currently looking to see if there are any other services

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Michael Dürig
Hi, No it isn't. Commit hooks haven't been designed for this type of dynamicity and generality. Exposing them at this layer has been considered way to dangerous and a breach of modularity. What has been done in the past for use cases requiring commit hook functionality on one hand and some

Re: CommitHooks as OSGi Components.

2016-09-12 Thread Tomek Rekawek
Hi Ian, > On 09 Sep 2016, at 18:04, Ian Boston wrote: > > Hi, > Is it possible write a CommitHook as an OSGI Component/Service and for Oak > to pick it up ? > The Component starts and gets registered as a service, but Oak doesn't > appear to pick it up. The standard

CommitHooks as OSGi Components.

2016-09-09 Thread Ian Boston
Hi, Is it possible write a CommitHook as an OSGI Component/Service and for Oak to pick it up ? The Component starts and gets registered as a service, but Oak doesn't appear to pick it up. If its not possible to add a CommitHook in this way, what is the best way of doing it from outside the