camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6674) Add allowNull option to @Converter to allow type converters to return null as valid response for special use-cases
Date Mon, 02 Sep 2013 08:53:52 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-6674:
-------------------------------

    Affects Version/s:     (was: 2.12.0)
        Fix Version/s:     (was: 2.12.1)
                       2.12.0
    
> 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
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.2, 2.12.0
>
>
> 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

Mime
View raw message