[
https://issues.apache.org/jira/browse/CXF-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138185#comment-16138185
]
Matthew Buckett commented on CXF-7483:
--------------------------------------
Yes, it does attempt to recover from the exception (so not swallowed), but when
developing code being able to see the exception without resorting to a debugger
is much more useful.
I think I'd prefer it behaved the same way as a standard Spring application
context, in that when autowiring fails you just throw the exception back to the
caller, rather than creating an un-autowired bean which will then probably fail
further along in the running application. But I realise that some people might
be relying on this behaviour which was why I was initially suggesting logging.
> JAXRSServerFactoryBeanDefinitionParser doesn't log autowire failures
> --------------------------------------------------------------------
>
> Key: CXF-7483
> URL: https://issues.apache.org/jira/browse/CXF-7483
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.1.7
> Reporter: Matthew Buckett
>
> I was using the scanning through spring XML config:
> {code:xml}
> <beans
> xmlns:jaxrs="http://cxf.apache.org/jaxrs";>
> <!-- snipped -->
> <jaxrs:server address="/rest" basePackages="org.example.rest">
> </jaxrs:server>
> <!-- snipped -->
> </beans>
> {code}
> and my autowiring was failing and I was ending up with a un-autowired bean
> instead. Debugging this was tricky and it was because
> {{org.apache.cxf.jaxrs.spring.JAXRSServerFactoryBeanDefinitionParser#createBeansFromDiscoveredClasses}}
> doesn't log anything when autowiring fails, it would be helpful if it either
> threw the exception showing where the problem was or logged it and said it
> was creating an non-autowired bean.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
