Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8228B200CC5 for ; Tue, 11 Jul 2017 13:38:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7EEB2163E24; Tue, 11 Jul 2017 11:38:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C3B4B163E22 for ; Tue, 11 Jul 2017 13:38:45 +0200 (CEST) Received: (qmail 82778 invoked by uid 500); 11 Jul 2017 11:38:45 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 82767 invoked by uid 99); 11 Jul 2017 11:38:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2017 11:38:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 86FB8195CCA for ; Tue, 11 Jul 2017 11:38:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id jkEKZctUBIB8 for ; Tue, 11 Jul 2017 11:38:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AB87161282 for ; Tue, 11 Jul 2017 11:15:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id EE12AE0069 for ; Tue, 11 Jul 2017 11:15:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 04026246A0 for ; Tue, 11 Jul 2017 11:15:00 +0000 (UTC) Date: Tue, 11 Jul 2017 11:15:00 +0000 (UTC) From: "Dennis Kieselhorst (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CXF-7442) Improve handling of JSR 310 Date Time API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 11 Jul 2017 11:38:46 -0000 Dennis Kieselhorst created CXF-7442: --------------------------------------- Summary: 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 datatype is a JSR 310 Date Type 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)