Expand my Community achievements bar.

Nomination window for the Adobe Community Advisor Program, Class of 2025, is now open!
SOLVED

Are event properties like resourceAddedAttributes and resourceChangedAttributes no longer supported in AEM 6.3?

Avatar

Level 3

We have a listener that's failing on us that has a filter that has filters like this.

(resourceType=ourOurg/components/content/ourComponent)

(resourceChangedAttributes=ctaPath)

(path=/content/*)

What's happening is that the event isn't firing. When I remove these filters and leave behind the path filter the event fires, but when I debug it it's missing those properties.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I thinks , this is duplicate post for AEM 6.3 Event problem



Arun Patidar

View solution in original post

4 Replies

Avatar

Community Advisor

Hi,

It seems, it is deprecated you can try to use ResourceChangeListerner instead.

org.apache.sling.api.SlingConstants.TOPIC_RESOURCE_CHANGED

Register a ResourceChangeListener instead

http://static.javadoc.io/org.apache.sling/org.apache.sling.api/2.11.0/deprecated-list.html

Thanks

Arun



Arun Patidar

Avatar

Level 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.

Avatar

Correct answer by
Community Advisor

I thinks , this is duplicate post for AEM 6.3 Event problem



Arun Patidar

Avatar

Level 3

I think you're right in hindsight. Fixing this.