[ https://issues.apache.org/jira/browse/CAMEL-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911236#comment-16911236 ]
Claus Ibsen edited comment on CAMEL-13870 at 8/21/19 8:17 PM: -------------------------------------------------------------- TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel - fix camel-activemq / camel-amqp which should reuse camel-jms configurer *DONE* - make endpoint configurer map of options static and use a bi-arg functional consumer for the setter/getter was (Author: davsclaus): TODOs - Endpoints with missing getter/setter paris *DONE* - Endpoints using delegate configuration class via UriParams (we need to know whats the delegate method) *DONE* - Dynamic properties via multi valued and property prefix would still be reflection based (httpClient.xxx=aaa&httpClient.yyy=bbb) - Consider remove support for consumer.xxx as we dont really need this anymore - Allow to turn this on|off per endpoint so component developers can opt out *DONE* - Setting boolean should restrict to true|false string values *DONE* - Also generate for component's so we have for both endpoint and components - Fix camel-cxf as it has some "oddities" *DONE* - Fix camel-jetty as it has some "oddities" *DONE* - Fix camel-atomix as it has some "oddities" *DONE* - Fix camel-cmis as it has some "oddities" *DONE* - Fix camel-crypto-cms as it has some "oddities" *DONE* - Fix camel-irc60870 as it has some "oddities" *DONE* - Fix camel-spring-ws as it has some "oddities" *DONE* - Fix camel-log as it has some "oddities" *DONE* - Rename apt json metadata to use configurationClassName instead of nested naming *DONE* - Omit getters as we dont need them for setting fast properties - Fix camel-log so we use fast configurs for the log formatter options (its coded in a special way) - Consider a way of gather usage statistics of introspection usage so we can find out how much reflection discovery we do with Camel - fix camel-activemq / camel-amqp which should reuse camel-jms configurer > camel3 - Fast configuring of endpoint options > --------------------------------------------- > > Key: CAMEL-13870 > URL: https://issues.apache.org/jira/browse/CAMEL-13870 > Project: Camel > Issue Type: Improvement > Reporter: Claus Ibsen > Assignee: Claus Ibsen > Priority: Major > Fix For: 3.x > > > Like we did for fast property placeholders on EIPs we can optimize endpoints > as well, by using the apt compiler plugin to generate a configurer classes > that uses direct java method invocations and then the property builder > support class can detect that we have such a configurer and use it, when it > looks for the setter. -- This message was sent by Atlassian Jira (v8.3.2#803003)