Properties: JCR node-event listener listens to wrong event

The JCR node-event listener for invalidating the properties cache listens to the node-added event (as per Spring config). As the primary intent of the cache invalidation is to make (published) changes to the properties file(s) available, the node-added event is inappropriate, because it is fired when the properties document goes into edit mode, but not when the document is published. On a project, I found that using the "property changed" event is more suitable for Release 7.7. On Release 7.8, there will be a new, higher-level event mechanism, which seems more appropriate to solve this problem than a listener at the JCR level.