camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Bokde (JIRA)" <>
Subject [jira] [Reopened] (CAMEL-8269) camel-salesforce: support for Salesforce Apex API
Date Mon, 04 May 2015 19:26:08 GMT


Dhiraj Bokde reopened CAMEL-8269:

Reopening to fix some mapping issues in new types added for API 33.0. 

> camel-salesforce: support for Salesforce Apex API
> -------------------------------------------------
>                 Key: CAMEL-8269
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-salesforce
>    Affects Versions: 2.14.1
>         Environment: n/a
>            Reporter: Daniel Pocock
>            Assignee: Dhiraj Bokde
>              Labels: rest, salesforce
>             Fix For: 2.14.2, 2.15.0
> Salesforce provides a service that they call the "Apex" API.
> Using Apex, a developer can write a script and upload it into and have
it executed in the server, similar to putting a stored procedure into a database.  The Apex
language is very similar to Java and likely to be very accessible to Camel developers.
> Here is an example:
> Notice that each method implementd in the Apex system can define new URLs for handling
REST requests.  The URL, the format of input data and the format of the return value are arbitrary
and at the discretion of the developer.  It is not uncommon for developers to use SObjects
as input or output and the existing DTOs from the camel-salesforce component would be suitable
for interaction with Apex.
> A typical use case for the Apex API is implementing the convertLead method for REST.
 The Salesforce SOAP API provides a mechanism for developers to request lead conversion. 
The Salesforce REST API does not have the convertLead() method.  The simplest and most common
way to work around this limitation is to implement convertLead() in Apex, here is an example:

This message was sent by Atlassian JIRA

View raw message