[
https://issues.apache.org/jira/browse/CXF-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-874.
-----------------------------
Resolution: Fixed
Well, resolved fixed as best we can at this point.
> Problems with service beans that use AOP
> ----------------------------------------
>
> Key: CXF-874
> URL: https://issues.apache.org/jira/browse/CXF-874
> Project: CXF
> Issue Type: Bug
> Components: Bus, Configuration, Core, JAX-WS Runtime
> Affects Versions: 2.0, 2.0.1
> Environment: Platform Independent
> Reporter: Zarar Siddiqi
> Assignee: Daniel Kulp
> Fix For: 2.0.2
>
>
> There are a couple threads on the mailing list that talk about some problems
> users are having when using AOP with CXF. Most notably there seem to be
> issues when service implementations are either proxied using AOP and/or are
> transactional in nature. Here is an example of this:
> http://www.nabble.com/Dependency-Injection-in-JAXWS-endpoint-tf4154573.html#a11884767
> As Brad pointed out, the dev team is looking into this. However, I couldn't
> find a JIRA for this issue. There's also this thread which is similar in
> nature.
> http://www.nabble.com/webservice-proxied-with-trasaction-interceptor-throwing-errors-on-WSDL-generation-tf4161303.html#a11842296
> In my last comment for CXF-803
> (https://issues.apache.org/jira/browse/CXF-803#action_12516555) I point to a
> case where interceptors configured using annotations fail to get added to the
> interceptor chain when an AOP auto proxy creator is used
> (org.springframework.aop.framework.autoproxy.BeanNameAutoProxyCreator). If
> BeanNameAutoProxyCreator is defined as a Spring bean the annotations are not
> read, but if I comment out the BeanNameAutoProxyCreator, all is well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
