Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 28 Aug 2013 12:50:51 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12665913.1377694142365.46525.1377694251592@arcas>
In-Reply-To: <JIRA.12665913.1377694142365@arcas>
References: <JIRA.12665913.1377694142365@arcas>
Subject: [jira] [Created] (CAMEL-6674) Add allowNull option to @Converter to
 allow type converters to return null as valid response for special
 use-cases
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Claus Ibsen created CAMEL-6674:
----------------------------------

             Summary: Add allowNull option to @Converter to allow type converters to return null as valid response for special use-cases
                 Key: CAMEL-6674
                 URL: https://issues.apache.org/jira/browse/CAMEL-6674
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 2.11.1, 2.12.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.11.2, 2.12.1


See nabble
http://camel.465427.n5.nabble.com/Xpath-parameter-binding-NodeList-vs-Node-tp5738067.html

This avoids the situation with the NodeList -> Node converter that may return null the 1st time, and then its regarded as a misses for conversion in future attempts.

Just be annotation the method from
@Converter

to:
@Converter(allowNull = true)

Should allow to fix this. As then the type converter registry knows that a null response is valid.


--
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