You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/08/28 14:50:51 UTC
[jira] [Created] (CAMEL-6674) Add allowNull option to @Converter to
allow type converters to return null as valid response for special
use-cases
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