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

..

cache

AbstractFallbackTransactionAttributeSource's DefaultCacheKey takes targetClass into account (again)

2014-12-22 18:46:07 +01:00

context

Annotation post-processors clear old InjectionMetadata registrations on refresh

2014-12-23 14:02:00 +01:00

ejb

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

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

format

Polishing

2014-07-15 15:13:35 +02:00

instrument/classloading

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

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

jmx

Handle scoped proxy properly in MBeanExporter

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

jndi

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

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

remoting

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

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

scheduling

Revised scheduling lifecycle integration

2014-10-31 17:26:23 +01:00

scripting

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

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

stereotype

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

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

ui

Performance improvement

2014-10-24 10:53:40 +02:00

validation

Support @Validated at method level for overriding validation groups

2014-11-24 23:42:48 +01:00