On Wed, May 30, 2012 at 10:40 AM, megachucky <megachu...@googlemail.com> wrote: > Just for fun (and learning by doing), I have written a Salesforce component > for Apache Camel. It is not feature-complete, just some methods of the > Salesforce API are supported. >
Ah cool. This would be a nice addition. > There are two alternatives for communicating with Salesforce: > > 1) Use Java API (this is what it did for my component): My favorite, but the > user has to create a company-specific WSDL file and generate Java classes. > See > http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_quickstart_steps.htm > > 2) Use REST API: Do simple HTTP(S) calls. > > IMO, using Java API is much more comfortable for development. However, I > think it is ugly and a no-go that every user of the salesforce component has > to create its own classes ?! If I write a component which should be added to > an upcoming Camel release, then I have to use REST API, right? > What API / Library do you have to use for doing REST calls from a Java > component? > Yeah REST seems the way projects go now for offering service APIs. In Camel there is the - camel-restlet - camel-cxf RS (dont support async client invocations) And then camel-ahc. http://camel.apache.org/ahc I like this AHC library. Its very lightweight and async https://github.com/sonatype/async-http-client#readme And its docs, there is a menu with user guides and whatnot http://sonatype.github.com/async-http-client/ > ----- > Best regards, > Kai Wähner > > Twitter: @KaiWaehner > Email: kont...@kai-waehner.de > Blog: www.kai-waehner.de/blog > -- > View this message in context: > http://camel.465427.n5.nabble.com/Salesforce-Component-Design-Questions-tp5713724.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
