[ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Carman updated CAMEL-6768: -------------------------------- Comment: was deleted (was: I don't mean we would have two different attributes on each annotation. I mean we would use a different attribute name for these specific cases. For instance, since the @Header is optional already, perhaps it gets a new attribute named "required" and you would set that to true to change the default behavior. For @Body, the attribute name would be called "optional" and you would again set that to true to change the default behavior. Just a thought. ) > @Header @Body @Property bean parameter binding - add mandatory option > --------------------------------------------------------------------- > > Key: CAMEL-6768 > URL: https://issues.apache.org/jira/browse/CAMEL-6768 > Project: Camel > Issue Type: Improvement > Components: camel-core > Reporter: Claus Ibsen > Priority: Minor > Fix For: Future > > > See > http://stackoverflow.com/questions/18874641/add-string-to-camel-exchange-header-from-route?noredirect=1#comment27863978_18874641 > We could have an attribute mandatory = true, which is default true for these > bean parameter annotations. Then people can set it to false, if a @Header is > not mandatory (eg do not fail if the header is not present). -- This message was sent by Atlassian JIRA (v6.1#6144)