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

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

GitHub user kiransg opened a pull request:

    https://github.com/apache/camel/pull/1176

    CAMEL-10317: Added support to use Http synchronous client with Olingo…

    …2 Component

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Infosys/camel CAMEL-10317-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1176.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1176
    
----
commit 8672609245fac6db5c66a8271faf9865dffaae57
Author: Kiran Govindaiah <[email protected]>
Date:   2016-09-14T13:16:22Z

    CAMEL-10317: Added support to use Http synchronous client with Olingo2 
Component

----


> Add support to use Http synchronous client with Olingo2 Component
> -----------------------------------------------------------------
>
>                 Key: CAMEL-10317
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10317
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-olingo2
>    Affects Versions: 2.17.3
>            Reporter: Kiran G
>            Priority: Minor
>
> At present Olingo2 component only supports configuring Http Asynchronous 
> Client. Asynchronous client lagging behind in feature wrt features (but 
> steadily catching up). Using Synchronous client makes debugging issues 
> easier. Also, this will make things easier for those using ThreadLocals. 
> The proposed change provides an option to the user to choose between 
> Synchronous and Asynchronous client while keeping the Asynchronous client as 
> default and keeping the existing functionality intact.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to