First noticed this on our custom modules and worked around it by re-registering the custom interception points within the applications coldbox.cfc. Just noticed in testing that Coldbox modules like CBORM are having the same issue. Has anyone else had issues with this?
To clarify this seems to be affecting applications listening to events announced by a module from outside the module, for instance the CBORM module fires ORMPostUpdate and I have an interceptor in my application that is also listening for that event. The event is announced to my application but unless I register the custom interception point in my app the method is not fired. This is a change from the behavior in previous versions (we are moving from CB 5 rc1).
At first I thought the events might now be intentionally scoped to the module, but that doesn’t make alot of since without namespacing since there would still be collisions from interception points with the same name.
Any insights on if this is a bug or was intentional?