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

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

GitHub user tlehoux opened a pull request:

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

    CAMEL-10768: Dropbox component support specifying route params using headers

    This a patch to support setting options with headers for dropbox component. 
It's for all endpoint options except accessToken and clientIdentifier, for 
which, IMO, it was not relevant. 
    - remotePath
    - localPath
    - newRemotePath
    - uploadMode
    - query

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

    $ git pull https://github.com/tlehoux/camel master

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

    https://github.com/apache/camel/pull/1722.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 #1722
    
----
commit 1a544e57af3afb21c39c26edfaab98456472c9c9
Author: Thomas Lehoux <[email protected]>
Date:   2017-05-28T04:11:43Z

    Dropbox component support specifying route params using headers

----


> Dropbox component should support specifying route params using headers
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-10768
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10768
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-dropbox
>            Reporter: Tim Dudgeon
>             Fix For: Future
>
>
> Unlike similar components it seems that the Dropbox component does not allow 
> to specify key parameters (such as the file name) using headers.
> Doing so would make it much more useful.
> See discussion here:
> http://camel.465427.n5.nabble.com/Specifying-file-names-using-Dropbox-component-td5793105.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to