Stephane Nicoll cae217de94 Handle scoped proxy properly in MBeanExporter ...

Previously, if a bean has a scoped proxy and is annotated to be exposed
to the JMX domain, both the scoped proxy and the target instance were
exposed in the JMX domain, resulting in a duplicate entries. Worse, if
such bean defines an explicit name, the application wouldn't start
because of a name conflict.

This commit deals explicitely with scoped proxy and make sure to only
expose the relevant bean.

Issue: SPR-12529

2014-12-23 16:03:52 +01:00

..

java

Handle scoped proxy properly in MBeanExporter

2014-12-23 16:03:52 +01:00

resources

Consistent formatting of license headers, package javadocs, and import declarations

2014-10-21 01:44:07 +02:00