You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2020/10/27 11:09:00 UTC
[jira] [Created] (CAMEL-15764) Twilo camel case endpoint URI
options leads to reflective property binding
James Netherton created CAMEL-15764:
---------------------------------------
Summary: 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
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)