camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Bokde (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6428) Salesforce Component
Date Wed, 05 Jun 2013 20:51:20 GMT

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

Dhiraj Bokde commented on CAMEL-6428:
-------------------------------------

Hi Babak, thanks for the ReflectiveOperationException fix, I missed that one. The test-salesforce-login.properties
should contain a Salesforce account for integration test, and I am not sure we can check in
a shared one without it becoming a security issue. 

Its easy to create a personal developer account on developerforce.com and create the Merchandise
schema by following Tutorial 1 and 2 at http://www.salesforce.com/us/developer/docs/workbook/index.htm

The plugin is dependent on the component and not a generic Camel plugin. I think that's why
Claus advised that it be co-located with the component. 
                
> Salesforce Component
> --------------------
>
>                 Key: CAMEL-6428
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6428
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.12.0
>            Reporter: Dhiraj Bokde
>            Assignee: Claus Ibsen
>              Labels: patch
>             Fix For: 2.12.0
>
>         Attachments: salesforce-component-201306050258.patch
>
>
> Submitting a new component for Salesforce support
> Supports Salesforce REST (including blob field retrieval), Batch, and Streaming APIs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message