@ManagedResource not discovered if at least one method is @Transactional, and no exception thrown [SPR-14189]

teo sarca opened SPR-14189 and commented

Consider following example

@Service
@ManagedResource(...)
public void MyService
{
  @ManagedOperation(....)
   public void myJmxMethod() { ... }

  @Transactional
  public void someOtherTransactionalMethod();
}

This managed resource will not be detected nor registered because in org.springframework.jmx.export.MBeanExporter.autodetect(AutodetectCallback), the call "beanFactory.getType(beanName)" returns "Proxy" class so "callback.include(beanClass, beanName)" will not detect it.

I find this issue critical because it's so easy to break a managed resource that was working just by annotating with @Transactional one of the methods, even if that method is not exposed.

Affects: 4.2.5

Issue Links:

• #6970 @Transactional annotation hodes @ManagedResource

Start in org.springframework.jmx.export.MBeanExporter.autodetect(AutodetectCallback), where beanFactory.getType(beanName) returns a proxy and callback.include is evaluated. Trace how @ManagedResource and @ManagedOperation discovery handles proxied beans, then verify that adding @Transactional to another method does not prevent registration or raise an exception. The issue does not name a test file.