cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gyorgy Orban (JIRA)" <j...@apache.org>
Subject [jira] Created: (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
Date Fri, 03 Apr 2009 14:46:12 GMT
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
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: CXF-2152
                 URL: https://issues.apache.org/jira/browse/CXF-2152
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 2.1.4
            Reporter: Gyorgy Orban
         Attachments: SpringAopClassHelper.patch

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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message