I don't even see that workflow. What did we do wrong? That's my question.

arunp99088702​ - I just tried a sample of an EventListener and it worked. I was able to see which property changed. In their sample code ACS Commons warns against using this often, it seems, saying...This is why I've been trying to get the ResourceChangeListener to work. Plus it seems more precise. ...

So like I said in my own thread I opened​, I'm having trouble with the ResourceChangeListener. I haven't tried an EventListener yet. I'm worried that I'll go to the trouble of implementing it and land in the same place.

You're using the EventListener, it looks like. Like the user above I tried a ResourceListener like this. I tried this code from Stack Overflow as a sanity check. When I debug this the addedPropertyNames and changedPropertyNames properties of "change" are null. I would expect to see what changed here...

Sorry, I'm not sure if I'm misunderstanding, but the problem I'm seeing that's similar is I don't see the property changed / property added messages from Events. It appears to have been removed in AEM 6.3.              

I tried that and the data  what changed is null. So I can (through either the event handler or the resource changed listener) listen for resource changes. It just looks like the subsystem won’t tell me what actually changed, which is what I need to fix this service.

Why was this never addressed? We're having the same problem over a year later.

Brightcove informed us today that 5.3.1, although listed on the same site as 5.1.6, isn't ready yet. We went back to 5.1.6 and things are working better.

navinkaushalThis isn't a system jar. The Brightcove Connector gets added to your codebase as source if you choose to modify it. When the maven build runs it creates a bundle and deploys it AEM the same as the rest of your code. I've learned in the last 2 weeks that along the way it bundles up bright...

Hermant,Maybe I'm not following what you're saying, but I tried embedding this jar as a dependency and it didn't work. In fact, my local environment stopped working where it was working before.