[
https://issues.apache.org/jira/browse/CXF-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087065#comment-16087065
]
Dennis Kieselhorst commented on CXF-7442:
-----------------------------------------
Hi Sergey, I first thought registering oob with a major release should be ok,
but I'm also fine with just adding them.
One class for all types would get fairly big that's why I would go for
JavaTimeTypesParamConverterProvider which contains ParamConverters for
LocalDate, LocalTime, LocalDateTime, OffsetDateTime, OffsetTime, ZonedDateTime.
> Improve handling of JSR 310 Date Time API
> -----------------------------------------
>
> Key: CXF-7442
> URL: https://issues.apache.org/jira/browse/CXF-7442
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Affects Versions: 3.1.12
> Reporter: Dennis Kieselhorst
> Fix For: 3.2.0
>
>
> If a wrong date is given as param, the type is a JSR 310 Datatype and an
> XmlAdapter is used, it will result in a ClassCastException. Moreover the
> catch block in org.apache.cxf.jaxrs.utils.JAXBUtils.useAdapter logs using
> ex.printStackTrace(). I created a testcase in
> org.apache.cxf.jaxrs.utils.InjectionUtilsTest#testJsr310DateExceptionHandling.
> In my view it should end up in IllegalArgumentException/
> createParamConversionException as for other invalid params.
> General question: Since CXF 3.2 depends on Java 8 do we want to make JSR 310
> handling more convenient so that XmlAdapter stuff is no longer required?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
