This is the second article with demo code (the first is a Composite HR Application Demo) to illustrate object-to-service mapping, which is the generalization of object-to-relational mapping to include anything callable from java. It is a technology that enables dynamic orchestration of services.
The main goal of this tutorial is to map POJOs (Plain Old Java Objects) to the data hidden behind the services provided by Salesforce.com.What do you think about the idea of object-to-service mapping?
The tutorial is split into two parts. In the first one, we show how to read data from Salesforce.com. In the second part, we explain how to create, update and delete Salesforce.com objects.
The example followed in this tutorial is a simple Customer Relationship Management (CRM) application, with three types of objects: Customers (corresponding to Salesforce.com "Account" objects), Opportunities and Contacts. Each type is described with its POJO class, and then mapped to the data hidden behind Salesforce.com web service.