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

Allow @ManagedXYZ on interfaces [SPR-3635] #8316

Closed
spring-projects-issues opened this issue Jun 29, 2007 · 1 comment
Closed

Allow @ManagedXYZ on interfaces [SPR-3635] #8316

spring-projects-issues opened this issue Jun 29, 2007 · 1 comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jun 29, 2007

Kenny MacLeod opened SPR-3635 and commented

Take the following code:

@ManagedResource
class X implements Y {

String getProp() { ... }
}

interface Y {
@ManagedAttribute
String getProp();
}

Intuitively, when a bean of type X is exposed through JMX, it would have getProp() exposed as a JMX attribute. However, it only exposes attributes/operations that are declared in X itself.

For consistency with @Transactional annotations, I think it should search superclasses and implemented interfaces for @Managed anootations and act accordingly.


Affects: 2.0.6

Issue Links:

Referenced from: commits 8f6a42b

5 votes, 5 watchers

@spring-projects-issues
Copy link
Collaborator Author

Kenny MacLeod commented

House-cleaning old unresolved reports. Any thoughts on this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant