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 6074110B6A for ; Wed, 24 Apr 2013 17:17:16 +0000 (UTC) Received: (qmail 61098 invoked by uid 500); 24 Apr 2013 17:17:16 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 61069 invoked by uid 500); 24 Apr 2013 17:17:16 -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 61060 invoked by uid 99); 24 Apr 2013 17:17:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Apr 2013 17:17:16 +0000 Date: Wed, 24 Apr 2013 17:17:16 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CAMEL-6307) Regression in 2.11.0 bean invocation 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/CAMEL-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6307. -------------------------------- Resolution: Fixed Fix Version/s: 2.12.0 2.11.1 Thanks for reporting > Regression in 2.11.0 bean invocation > ------------------------------------ > > Key: CAMEL-6307 > URL: https://issues.apache.org/jira/browse/CAMEL-6307 > Project: Camel > Issue Type: Bug > Components: camel-core > Affects Versions: 2.11.0 > Environment: N/A > Reporter: David J. M. Karlsen > Assignee: Claus Ibsen > Labels: argument, beaninvocation, parse > Fix For: 2.11.1, 2.12.0 > > > When upgradring from 2.10.2 to 2.11.0 I met this regression: > I have a step in my route which invokes a bean: > {noformat} > > {noformat} > after the upgrade it threw: > {noformat} > org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[Message: BeanInvocation public abstract com.mycomp.Transfer com.mycomp.TransferService.doTransfer(com.mycomp.Transfer) with [com.mycomp.Transfer@7e299629[.....]]]] > Caused by: org.apache.camel.NoTypeConversionAvailableException: No type converter available to convert from type: java.lang.String to the required type: com.mycomp.Transfer with value > at org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:181) ~[camel-core-2.11.0.jar:2.11.0] > at org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:149) ~[camel-core-2.11.0.jar:2.11.0] > at org.apache.camel.component.bean.MethodInfo$2.evaluateParameterValue(MethodInfo.java:540) ~[camel-core-2.11.0.jar:2.11.0] > {noformat} > If I change the route to: > {noformat} > > {noformat} > (notice if no whitespace before/after ${body} it works as before). > The problematic code seems to be in org.apache.camel.component.bean.MethodInfo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira