Allow @ManagedResource to be used with @Bean methods [SPR-9908]

[spring-projects-issues]

Phil Webb opened SPR-9908 and commented

@ManagedResource should be allowed on @Bean methods in @Configuration classes. Otherwise it is not possible to expose a bean via annotations for which you do not have the source for.

---

Affects: 3.1.2

Issue Links:

• MBeanExporter should use annotations if @ManagedResource present, otherwise use defaults [SPR-11298] #15922 MBeanExporter should use annotations if @ManagedResource present, otherwise use defaults
• Allow the ManagedResource/Attribute/Metric/Operation to be placed on interface [SPR-13138] #17729 Allow the ManagedResource/Attribute/Metric/Operation to be placed on interface

[spring-projects-issues]

Stéphane Nicoll commented

I am curious. What bean would that be? Does it have @ManagedXYZ on operations and attributes you wish to expose?

[spring-projects-issues]

Phil Webb commented

I'm not sure, it's been a long time since I looked at this issue. Perhaps the use-case isn't really justified, clearly there haven't been a lot of votes for the feature. I'd be tempted to close this one until someone else asks for it. I don't think I ever had a direct need for it, it just seemed like something that might be useful.

[spring-projects-issues]

Stéphane Nicoll commented

The reason why I am asking is because we would need additional meta-data on the target type to figure out what to export (operations, attributes, etc). So if the target class is not an MBean or if it hasn't the proper meta-data (annotations) nothing would really happen at this point. I was hoping you could shade some light on the use case...

Alright, let's close this one for now then.

[spring-projects-issues]

Stéphane Nicoll commented

The reason why I am asking is because we would need additional meta-data on the target type to figure out what to export (operations, attributes, etc). So if the target class is not an MBean or if it hasn't the proper meta-data (annotations) nothing would really happen at this point. I was hoping you could shade some light on the use case...

Alright, let's close this one for now then.