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] [Commented] (CAMEL-6768) @Header @Body @Property bean parameter binding - add mandatory option
Date Wed, 02 Oct 2013 06:30:26 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783700#comment-13783700
] 

Claus Ibsen commented on CAMEL-6768:
------------------------------------

There may be an issue with have only 1 attribute and then having 2+ in an annotation. If you
have 1 attribute you dont have to specify the name. But having 2 you may have to specify both.
Though not exactly sure whats the story is, or if you can name one of  the attributes as value
and that would be the non-named attribute.


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

Mime
View raw message