You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Gyorgy Orban (JIRA)" <ji...@apache.org> on 2009/04/03 16:46:12 UTC

[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

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.

[jira] Updated: (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

Posted by "Gyorgy Orban (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyorgy Orban updated CXF-2152:
------------------------------

    Attachment: SpringAopClassHelper.patch

> 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.

[jira] Assigned: (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

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp reassigned CXF-2152:
--------------------------------

    Assignee: Daniel Kulp

> 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
>            Assignee: Daniel Kulp
>         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.

[jira] Resolved: (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

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-2152.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.1
                   2.1.5
                   2.0.11

> 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
>            Assignee: Daniel Kulp
>             Fix For: 2.0.11, 2.1.5, 2.2.1
>
>         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.