Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beans proxied by the Spring container with declared CQs are not registered and triggered [DATAGEODE-53] #104

Closed
spring-projects-issues opened this issue Oct 23, 2017 · 0 comments
Assignees
Labels
in: configuration in: cq type: bug

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Oct 23, 2017

John Blum opened DATAGEODE-53 and commented

When beans declared in the Spring container are proxied (to apply and "decorate" those beans with additional capabilities, e.g. Caching, Security or Transaction Management, basically any "cross-cutting" concern where an AOP Proxy is applied), then a CQ annotated callback service method is not identified properly, and subsequently, the CQ is never registered and triggered accordingly


Affects: 2.0 GA (Kay)

Backported to: 2.0.1 (Kay SR1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: configuration in: cq type: bug
Projects
None yet
Development

No branches or pull requests

2 participants