Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
From: zregvart <git@git.apache.org>
To: dev@camel.apache.org
Reply-To: dev@camel.apache.org
Message-ID: <git-pr-1274-camel@git.apache.org>
Subject: [GitHub] camel pull request #1274: CAMEL-10478 Support simple language expressions in...
Content-Type: text/plain
Date: Mon, 14 Nov 2016 20:46:29 +0000 (UTC)
archived-at: Mon, 14 Nov 2016 20:46:31 -0000

GitHub user zregvart opened a pull request:

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

    CAMEL-10478 Support simple language expressions in header values in camel-salesforce

    This is a PR against 2.18.x, as this functionality would be beneficial to 2.18
    users as well.
    
    Implements support for simple language expressions in header values for
    the camel-salesforce component.
    
    AbstractSalesforceProcessor was modified to post-process values
    retrieved from message header and evaluate them with simple language.
    This greatly simplifies usage in downstream salesforce components as
    they can have access upstream values. For instance:
    
        salesforce:queryMore?sObjectQuery=${header.nextRecordsUrl}...

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

    $ git pull https://github.com/zregvart/camel CAMEL-10478-camel-2.18.x

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

    https://github.com/apache/camel/pull/1274.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 #1274
    
----
commit 6a28486d6714672ea67a40331d339df506aa1db2
Author: Zoran Regvart <zoran@regvart.com>
Date:   2016-11-14T20:45:07Z

    Support simple language expressions in header values in camel-salesforce
    
    Implements support for simple language expressions in header values for
    the camel-salesforce component.
    
    AbstractSalesforceProcessor was modified to post-process values
    retrieved from message header and evaluate them with simple language.
    This greatly simplifies usage in downstream salesforce components as
    they can have access upstream values. For instance:
    
        salesforce:queryMore?sObjectQuery=${header.nextRecordsUrl}...

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---