@sberyozkin @jwcarman It does indeed look like this change will break the JAX-RS TCK... here are the tests that fail as a result of this change (plus #445): ``` [javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jaxrs/api/rs/core/link/JAXRSClient.java#fromResourceMethodLinkUsedInInvocationTest_from_standalone [javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jaxrs/ee/rs/container/requestcontext/JAXRSClient.java#getHeadersIsMutableTest_from_standalone [javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jaxrs/spec/provider/standardnotnull/JAXRSClient.java#clientBigDecimalProviderTest_from_standalone [javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jaxrs/spec/provider/standardnotnull/JAXRSClient.java#clientBooleanProviderTest_from_standalone [javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jaxrs/spec/provider/standardnotnull/JAXRSClient.java#clientCharProviderTest_from_standalone [javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jaxrs/spec/provider/standardnotnull/JAXRSClient.java#clientIntegerProviderTest_from_standalone ```
I will continue to look into these failures - my guess is that we are either missing something (i.e. handling of null values, etc.) or that the TCK is making some assumptions. If it is the latter, we can challenge the TCK tests. [ Full content available at: https://github.com/apache/cxf/pull/446 ] This message was relayed via gitbox.apache.org for [email protected]
