Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 52EB81734D for ; Sun, 5 Apr 2015 05:27:33 +0000 (UTC) Received: (qmail 60077 invoked by uid 500); 5 Apr 2015 05:27:33 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 60032 invoked by uid 500); 5 Apr 2015 05:27:33 -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 60020 invoked by uid 99); 5 Apr 2015 05:27:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2015 05:27:33 +0000 Date: Sun, 5 Apr 2015 05:27:33 +0000 (UTC) From: "Dmitry Kozlov (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-6331) Wrap exceptions in JAXRSBeanValidationInvoker into Fault so that these exceptions are exposed to ExceptionMapper-s MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kozlov updated CXF-6331: ------------------------------- Description: As of now only {{ConstraintValidationExceptions}} thrown within {{JAXRSBeanValidationInvoker.invoke(..)}} method are exposed to {{ExceptionMapper}} processing chain. But both validation framework and underlying validators can throw any other unchecked non-{{ConstraintValidationException}}-s, e.g. {{ValidationExceptions}} or any other {{RuntimeException}}. At the same time only {{Fault}} causes are exposed to {{ExceptionMapper}} chain within {{JAXRSInvoker}}. Please kindly wrap any non-{{Fault}} exceptions thrown within {{JAXRSBeanValidationInvoker.invoke(..)}} method into {{Fault}} instances so that they could be properly handled by exception mappers. was: As of now only {{ConstraintValidationExceptions}} thrown within {{JAXRSBeanValidationInvoker.invoke(..)}} method are exposed to {{ExceptionMapper}} processing chain. But both validation framework and underlying validators can throw any other unchecked non-{{ConstraintValidationException}}s, e.g. {{ValidationExceptions}} or any other {{RuntimeException}}. At the same time only {{Fault}} causes are exposed to {{ExceptionMapper}} chain within {{JAXRSInvoker}}. Please kindly wrap any non-{{Fault}} exceptions thrown within {{JAXRSBeanValidationInvoker.invoke(..)}} method into {{Fault}} instances so that they could be properly handled by exception mappers. > Wrap exceptions in JAXRSBeanValidationInvoker into Fault so that these exceptions are exposed to ExceptionMapper-s > ------------------------------------------------------------------------------------------------------------------ > > Key: CXF-6331 > URL: https://issues.apache.org/jira/browse/CXF-6331 > Project: CXF > Issue Type: Bug > Components: JAX-RS > Affects Versions: 3.0.4 > Reporter: Dmitry Kozlov > > As of now only {{ConstraintValidationExceptions}} thrown within {{JAXRSBeanValidationInvoker.invoke(..)}} method are exposed to {{ExceptionMapper}} processing chain. > But both validation framework and underlying validators can throw any other unchecked non-{{ConstraintValidationException}}-s, e.g. {{ValidationExceptions}} or any other {{RuntimeException}}. > At the same time only {{Fault}} causes are exposed to {{ExceptionMapper}} chain within {{JAXRSInvoker}}. > Please kindly wrap any non-{{Fault}} exceptions thrown within {{JAXRSBeanValidationInvoker.invoke(..)}} method into {{Fault}} instances so that they could be properly handled by exception mappers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)