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

ASF GitHub Bot commented on CAMEL-12442:
----------------------------------------

onderson commented on a change in pull request #2314: CAMEL-12442:rest-dsl - 
Rest producer should use RestConfiguration
URL: https://github.com/apache/camel/pull/2314#discussion_r185699459
 
 

 ##########
 File path: 
components/camel-http/src/main/java/org/apache/camel/component/http/HttpComponent.java
 ##########
 @@ -312,6 +312,26 @@ public Producer createProducer(CamelContext camelContext, 
String host,
         if (!ObjectHelper.isEmpty(uriTemplate)) {
             url += "/" + uriTemplate;
         }
+        
+        RestConfiguration config = configuration;
 
 Review comment:
   I would suggest a default method in an interface and implementing in all 
components to avoid similar code piece in every component.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> rest-dsl - Rest producer should use RestConfiguration
> -----------------------------------------------------
>
>                 Key: CAMEL-12442
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12442
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 2.22.0
>
>
> The RestConfiguration have additional configuration for component level, 
> endpoint level which you may want to allow to configure for the rest-dsl 
> producer side.
> Currently this is only supported on the consumer side.
> To introduce this, requires an API change in the RestProducerFactory method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to