Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Ce contenu n'est pas disponible dans la langue sélectionnée.
56.4. Nullable Options
Overview Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
In some cases, it can make sense to let method arguments default to
null. But this is not allowed by default. If you want to allow some of your method arguments from the Java API to take null values, you must declare this explicitly using the nullableOptions element.
Syntax Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
The
nullableOptions element can be defined with one or more nullableOption child elements, as follows:
<nullableOptions> <nullableOption>ArgumentName</nullableOption> ... </nullableOptions>
<nullableOptions>
<nullableOption>ArgumentName</nullableOption>
...
</nullableOptions>
Where
ArgumentName is the name of a method argument from the Java API.
Scope Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
As shown in the following extract, the
nullableOptions element can optionally appear as a child of the apis element and/or as a child of api elements:
You can define the
nullableOptions element at the following scopes:
- As a child of an
apielement—thenullableOptionsmappings apply only to the API class specified by theapielement. - As a child of the
apiselement—thenullableOptionsmappings apply to all API classes by default, but can be overridden at theapilevel.
Example Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
The following example shows the nullable options declared for the
CompaniesResource proxy class from the Apache Camel LinkedIn component: