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 937DED4AE for ; Mon, 24 Sep 2012 08:42:12 +0000 (UTC) Received: (qmail 78907 invoked by uid 500); 24 Sep 2012 08:42:12 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 78758 invoked by uid 500); 24 Sep 2012 08:42:08 -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 78383 invoked by uid 99); 24 Sep 2012 08:42:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 08:42:07 +0000 Date: Mon, 24 Sep 2012 19:42:07 +1100 (NCT) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: <891376758.115925.1348476127861.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CAMEL-5644) Bean component - Should use try conversion when choosing method based on parameter type matching MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Claus Ibsen created CAMEL-5644: ---------------------------------- Summary: Bean component - Should use try conversion when choosing method based on parameter type matching Key: CAMEL-5644 URL: https://issues.apache.org/jira/browse/CAMEL-5644 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.9.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.9.4, 2.11.0, 2.10.2 When the bean component has to pick among overloaded methods, then it does best matching on parameter types etc. We should relax the type conversion to try attempt. -- 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