[jira] [Created] (CXF-7486) JAXRSServerFactoryBeanDefinitionParser should throw exception when autowiring fails.
Matthew Buckett created CXF-7486: Summary: JAXRSServerFactoryBeanDefinitionParser should throw exception when autowiring fails. Key: CXF-7486 URL: https://issues.apache.org/jira/browse/CXF-7486 Project: CXF Issue Type: Improvement Components: JAX-RS Affects Versions: 3.0.14 Reporter: Matthew Buckett Rather than logging an error JAXRSServerFactoryBeanDefinitionParser should throw the exception from the failure to autowire a bean. This would match the standard behaviour observed by from Spring when autowiring fails and make tracking down failures easier startup fails rather than getting a NullPointerException at runtime. As this could a breaking change it should only be introduced at a major upgrade and documented in the release notes. If there's time updating the log message produced to warn about this upcoming change may also be helpful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CXF-7483) JAXRSServerFactoryBeanDefinitionParser doesn't log autowire failures
[
https://issues.apache.org/jira/browse/CXF-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141409#comment-16141409
]
Matthew Buckett commented on CXF-7483:
--
Thanks for the helpful reply, I think you're right on the money about not
changing for the 3.2 release. I've created CXF-7486 to track the issue.
> 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
>Assignee: Sergey Beryozkin
> Fix For: 3.0.15, 3.1.13, 3.2.0
>
>
> I was using the scanning through spring XML config:
> {code:xml}
>xmlns:jaxrs="http://cxf.apache.org/jaxrs";>
>
>
>
>
>
> {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)
[jira] [Resolved] (CXF-6881) Implement JAX-RS 2.1
[ https://issues.apache.org/jira/browse/CXF-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-6881. --- Resolution: Fixed > Implement JAX-RS 2.1 > > > Key: CXF-6881 > URL: https://issues.apache.org/jira/browse/CXF-6881 > Project: CXF > Issue Type: Task > Components: JAX-RS >Reporter: Sergey Beryozkin > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CXF-7448) Enable use of reflection in JAX-RS client by default
[ https://issues.apache.org/jira/browse/CXF-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy McCright resolved CXF-7448. Resolution: Fixed > Enable use of reflection in JAX-RS client by default > > > Key: CXF-7448 > URL: https://issues.apache.org/jira/browse/CXF-7448 > Project: CXF > Issue Type: Improvement > Components: JAX-RS >Affects Versions: 3.2.0 >Reporter: Andy McCright > Fix For: 3.2.0 > > > Per discussion on the dev list, we should enable the use of reflection for > "non-standard" HTTP methods in the JAX-RS client. By default, the > HttpURLConnection will only allow "standard" HTTP methods, such as GET, PUT, > POST, DELETE, OPTIONS and HEAD. It does not include PATCH or other > user-defined methods and will throw an exception when a user attempts to use > one of these methods. > CXF already works around this issue by using reflection to set HTTP method > when a system property or message property is set. This bypasses the check > and allows the method to process. For CXF 3.2, I would like to make this > property enabled by default, so that these "non-standard" HTTP methods will > work by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (CXF-7448) Enable use of reflection in JAX-RS client by default
[ https://issues.apache.org/jira/browse/CXF-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy McCright closed CXF-7448. -- > Enable use of reflection in JAX-RS client by default > > > Key: CXF-7448 > URL: https://issues.apache.org/jira/browse/CXF-7448 > Project: CXF > Issue Type: Improvement > Components: JAX-RS >Affects Versions: 3.2.0 >Reporter: Andy McCright > Fix For: 3.2.0 > > > Per discussion on the dev list, we should enable the use of reflection for > "non-standard" HTTP methods in the JAX-RS client. By default, the > HttpURLConnection will only allow "standard" HTTP methods, such as GET, PUT, > POST, DELETE, OPTIONS and HEAD. It does not include PATCH or other > user-defined methods and will throw an exception when a user attempts to use > one of these methods. > CXF already works around this issue by using reflection to set HTTP method > when a system property or message property is set. This bypasses the check > and allows the method to process. For CXF 3.2, I would like to make this > property enabled by default, so that these "non-standard" HTTP methods will > work by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
