[jira] [Updated] (CAMEL-15764) Twilo camel case endpoint URI options leads to reflective property binding

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen updated CAMEL-15764:
--------------------------------
    Fix Version/s: 3.7.0

> Twilo camel case endpoint URI options leads to reflective property binding
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-15764
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15764
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-twilio
>    Affects Versions: 3.6.0
>            Reporter: James Netherton
>            Priority: Minor
>             Fix For: 3.7.0
>
>
> I noticed some inconsistency when adding native support for Twilio in Camel Quarkus. 
> Consider the following URI:
> twilio://incoming-phone-number/create?phoneNumber=RAW(+15005550006)
> Turns out that this leads to the phoneNumber property binding being done reflectively instead of via the configurer.
> This problem is that ignoreCase is always false here:
> https://github.com/apache/camel/blob/master/components/camel-twilio/src/generated/java/org/apache/camel/component/twilio/IncomingPhoneNumberEndpointConfigurationConfigurer.java#L33
> Hence the case logic attempts to match on the exact parameter name, and there is no case block for the camel cased 'phoneNumber'.
> The obvious workaround is to name the URI param 'phonenumber' or 'PhoneNumber' but the camel-twilio docs all refer to camel cased parameter names.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)