When integrating any non native application (JAVA or NET or ..) with salesforce, you need to have the salesforce API library in place that can be referred/used as a referenced library in project being developed. This library is the the one that acts as face to salesforce i.e., intermediary between your application and salesforce.
Simple yet important step of such type of integration is to generate stub code (jar file) from wsdl (salesforce enterprise or partner wsdl) and though such a simple step, we (at least I) always forget (or I should say cant recall easily) the step on how to generate same.
Below are three easy steps to generate stub code (jar) from a wsdl:
java -classpath wsc-xx.jar com.sforce.ws.tools.wsdlc *wsdl* *jar.file*
java -jar wsc-23.jar *wsdl* *jar.file*
wsdl is the name of the WSDL file
jar.file is the name of the output jar file that wsdlc generates
You can include an optional argument: -Dpackage-prefix=myprefix
With this you are all set with stub code / library and ready to make soap API calls to Salesforce.
Author : Chirag Mehta & Angelica Buffa
Using FTP servers to store and share files is very common now at days. Most language programs let you develop FTP clients and consume their services.
With Apex, there are three possible approaches to resolve the integration with this kind of file servers:
I – Data Loader CLI – Windows approach.
II – Java Web Service
III – Http Request
Apache Axis2 Eclipse Plugins allow Web service developers to easily and speedily expose the available plain old Java applications as Web services.
wso2.org lists a tutorial by Lahiru Sandakith which consists of two parts, with two examples that walk you through developing and deploying a sample Web service using the Top-down (Contract First) and Bottom-up (Code First) approach using Axis2 Eclipse Plugins.
The tutorial is written for Eclipse SDK v3.2 and Axis2 Eclipse Plugin v1.3.
Read the tutorial at http://wso2.org/library/1719