Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA9F517ECB for ; Tue, 13 Jan 2015 11:36:32 +0000 (UTC) Received: (qmail 48135 invoked by uid 500); 13 Jan 2015 11:36:34 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 48096 invoked by uid 500); 13 Jan 2015 11:36:34 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 48086 invoked by uid 99); 13 Jan 2015 11:36:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2015 11:36:34 +0000 Date: Tue, 13 Jan 2015 11:36:34 +0000 (UTC) From: "Benjamin Habegger (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-8237) Regression: no longer possible to use a custom DataFormat bean in rest configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Benjamin Habegger created CAMEL-8237: ---------------------------------------- Summary: Regression: no longer possible to use a custom DataFormat bean in rest configuration Key: CAMEL-8237 URL: https://issues.apache.org/jira/browse/CAMEL-8237 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.14.1 Reporter: Benjamin Habegger Previously in version 2.14.0 it was possible to define a dataFormat as a spring bean (as decribed in http://camel.apache.org/data-format.html) and set the rest configuration to use this custom dataformat. Since version 2.14.1, defining such a dataformat and configuring rest to use it leads to : java.lang.IllegalArgumentException: JsonDataFormat name: json must not be an existing bean instance from the registry -- This message was sent by Atlassian JIRA (v6.3.4#6332)