[jira] [Resolved] (CAMEL-12033) Rethink how default coapMethod URI option is handled

["James Netherton (JIRA)" <ji...@apache.org>]

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

James Netherton resolved CAMEL-12033.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.21.0

> Rethink how default coapMethod URI option is handled
> ----------------------------------------------------
>
>                 Key: CAMEL-12033
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12033
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-coap
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
>             Fix For: 2.21.0
>
>
> The CoAP endpoint has a {{coapMethod}} option which defaults to "*". This is used on the consumer to signify that all methods are allowed.
> However, no thought seems to have been given to how this is handled in the producer. There's a switch block with cases handling individual method names. But nothing for "*", hence the CoAP client is never invoked and no response is set on the message exchange.
> Maybe we make things like the camel HTTP components? {{coapMethod}} can be modified to {{coapMethodRestrict}} to deal with the consumer part.
> The method to use on the producer side can be inferred from whether we have a message payload (POST) or not (GET). Else we use pick the method from a header like {{CamelCoapMethod}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)