[CXF-2152] Certain Spring AOP proxies cannot be used any more as service bean since CXF 2.1.4 because the real (non-proxy) target class is not found correctly by SpringAopClassHelper

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.4
• Fix Version/s: 2.0.11, 2.1.5, 2.2.1
• Component/s: JAX-WS Runtime
• Assignee: Daniel Kulp
• Reporter: Gyorgy Orban
• Created: 03/Apr/09 14:45
• Updated: 24/Apr/09 21:17
• Resolved: 03/Apr/09 21:02

Description

This issue has come up because of a change in SpringAopClassHelper. There are two ways of creating a proxy with org.springframework.aop.framework.ProxyFactory: either by setting the target instance using the setTarget method, or using the setTargetClass method. If the latter is used, Advised.getTargetSource().getTarget() will return null, because no target instance exists. The former implementation of SpringAopClassHelper used AopUtils.getTargetClass, which handled the latter case correctly. Although the current implementation still uses AopUtils.getTargetClass, it never gets executed. Please find the patch attached that handles both types of aop proxies for us.