Jeff Douglas - Technology, Coding and Bears... OH MY! » Java http://blog.jeffdouglas.com Get your head out of your #@! and into the clouds! Thu, 02 Feb 2012 11:57:20 +0000 en hourly 1 http://wordpress.org/?v= Document Apex Code with ApexDoc http://blog.jeffdouglas.com/2011/01/27/document-apex-code-with-apexdoc/?utm_source=rss&utm_medium=rss&utm_campaign=document-apex-code-with-apexdoc http://blog.jeffdouglas.com/2011/01/27/document-apex-code-with-apexdoc/#comments Thu, 27 Jan 2011 15:04:46 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=3583

apex_doc_logo.png

My fellow Appirian and resident super-smart guy, Aslam Bari has created a super slick tool to document Apex code. ApexDoc is essentially JavaDocs for Apex. You add comments to your source code in the JavaDoc fashion (@author, @date, @param, etc) and ApexDoc reads these and generates a nice set of HTML files that allows you to browse your class structure. Here’s a short video on the entire process.

Generating the ApexDocs is fairly simple. Just point to your source code, an option output file, an optional file containing the HMTL for the right Home frame (project name, description, etc) and an optional file containing author information. Sample command syntax is:

apexdoc <source_directory> [<target_directory?>] [<homefile>] [<authorfile>]

Download ApexDoc here along with more detailed info and feedback.

apexdoc-screenshot.png

Update: Aslam and I worked on a bug affecting Mac and Unix users. Download the latest version of the files to get the fix. Also, here are some screenshots that may help out Mac users.

]]> http://blog.jeffdouglas.com/2011/01/27/document-apex-code-with-apexdoc/feed/ 1 Salesforce REST API Demo from Cloudstock http://blog.jeffdouglas.com/2010/12/17/salesforce-rest-api-demo-from-cloudstock/?utm_source=rss&utm_medium=rss&utm_campaign=salesforce-rest-api-demo-from-cloudstock http://blog.jeffdouglas.com/2010/12/17/salesforce-rest-api-demo-from-cloudstock/#comments Fri, 17 Dec 2010 17:18:16 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=3353

This is the demo that I put together for the Cloudstock Hackathon and I tried to throw in as many partner services as possible. I finally ended up with five so it was dubbed the “Kitchen Sink” demo. I thought some people may find it useful as it shows how to use the Force.com REST API in conjunction with OAuth2 using the Spring MVC framework. Pat Patterson put together a great Getting Started with the Force.com REST API article but my app is slightly different and IMHO easier, since it uses the Spring Framework.

The app is a external-facing recruiting site that advertises the open Appirio positions. Please remember that this is a demo and I put most of the code into a couple of controllers to make it easier to show. The code can definitely be refactored in certain places.

Here’s how the app uses the partner services:

Partner How Used?
Store pdf job descriptions on Box for download by applicants.
Use Force.com as the datastore for open jobs. Access to Force.com using OAuth2 and the REST API.
Send a job to a friend via SMS.
Application built using Spring STS, Spring Roo and Spring MVC. The application runs locally on tc Server.
Store metrics for jobs on MongoHQ.

Here’s a video of the application so you can see it in action plus some explanation of the Spring code. The controller code for the OAuth functionality and interacting with the Job records is following the jump.

It may be easier to watch this at Youtube with a larger picture. Just double-click the video.

www.youtube.com/watch?v=TFNJaHYEK3U

OAuthController

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125

package com.appirio.jobs.web;
 
import java.io.IOException;
import java.io.UnsupportedEncodingException;
import java.net.URLEncoder;
 
import org.apache.commons.httpclient.HttpClient;
import org.apache.commons.httpclient.methods.PostMethod;
import org.json.JSONException;
import org.json.JSONObject;
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.context.request.RequestAttributes;
import org.springframework.web.context.request.WebRequest;
 
/**
 * @author Jeff Douglas (jeff@appirio.com)
 */
@RequestMapping("/oauth/**")
@Controller
public class OAuthController {
 
  private static final String ACCESS_TOKEN = "ACCESS_TOKEN";
  private static final String INSTANCE_URL = "INSTANCE_URL";
 
  private String clientId = null;
  private String clientSecret = null;
  private String redirectUri = null;
  private String environment = null;
  private String authUrl = null;
  private String tokenUrl = null;
  private String accessToken = null;
 
  private void init() {
 
      redirectUri = "https://127.0.0.1:8443/AppirioCareers/oauth/_callback";
      environment = "https://na5.salesforce.com";
      // client id and secret from Force.com Remote Access
      clientId = "YOUR-CLIENT-ID";
      clientSecret = "YOUR-CLIENT-SECRET";
 
        try {
      authUrl = environment + "/services/oauth2/authorize?response_type=code&client_id=" 
        + clientId + "&redirect_uri=" + URLEncoder.encode(redirectUri, "UTF-8");
    } catch (UnsupportedEncodingException e1) {
      // TODO Auto-generated catch block
      e1.printStackTrace();
    }
 
        tokenUrl = environment + "/services/oauth2/token";
 
  }
 
  /* Start the OAuth process if no session with the access token is found. 
   * If a session exists, the redirect the user to the /job/list page. */
  @RequestMapping(value = "/oauth/start", method = RequestMethod.GET)
  public String startOauth(WebRequest req) {
 
    init();
    // check for an access token in the servlet session
    accessToken = (String) req.getAttribute(ACCESS_TOKEN, RequestAttributes.SCOPE_SESSION);
 
    if (accessToken != null) {
      System.out.println("Session found!! Access token: "+accessToken);
      return "forward:/job/list";
    } else {
      System.out.println("No session... need to auth.");        
      return "redirect:" + authUrl;
    }
 
  }
 
  /* OAuth callback from Force.com after authrozing the application.  */
  @RequestMapping(value = "/oauth/_callback", method = RequestMethod.GET)
  public String endOauth(WebRequest req) {
 
    init();
    String accessToken = null;
    String instanceUrl = null;
    String code = req.getParameter("code");
    HttpClient http = new HttpClient();
    PostMethod post = new PostMethod(tokenUrl);
    post.addParameter("client_secret", clientSecret);
    post.addParameter("redirect_uri", redirectUri);
    post.addParameter("grant_type", "authorization_code");
    post.addParameter("code", code);
    post.addParameter("client_id", clientId);
 
    try {
      JSONObject json = null;
      http.executeMethod(post);
      String respBody = post.getResponseBodyAsString();
      System.out.println("post response: " + respBody);
      try {
        json = new JSONObject(respBody);
        accessToken = json.getString("access_token");
        instanceUrl = json.getString("instance_url");
      } catch (JSONException e) {
        e.printStackTrace();
      }
      System.out.println("found access token: "+accessToken);
      System.out.println("found instance url: "+instanceUrl);
    } catch (IOException e) {
      // TODO Auto-generated catch block
      e.printStackTrace();
    } finally {
      post.releaseConnection();
    }
 
    System.out.println("Setting Access token: "+accessToken);
    System.out.println("Setting Instance Url: "+instanceUrl);
 
    /* Set the token and url to the session so other servlets can access it. */
    req.setAttribute(ACCESS_TOKEN, accessToken, RequestAttributes.SCOPE_SESSION);
    req.setAttribute(INSTANCE_URL, instanceUrl, RequestAttributes.SCOPE_SESSION);
 
    return "forward:/job/list";
  }
 
  @RequestMapping
  public String index() {
    return "oauth/index";
  }
}

JobController

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252

package com.appirio.jobs.web;
 
import java.io.IOException;
import java.net.UnknownHostException;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Map;
 
import org.apache.commons.httpclient.HttpClient;
import org.apache.commons.httpclient.HttpException;
import org.apache.commons.httpclient.NameValuePair;
import org.apache.commons.httpclient.methods.GetMethod; 
import org.json.JSONArray;
import org.json.JSONException;
import org.json.JSONObject;
import org.springframework.stereotype.Controller;
import org.springframework.ui.Model;
import org.springframework.web.bind.annotation.ModelAttribute;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.context.request.RequestAttributes;
import org.springframework.web.context.request.WebRequest;
import org.springframework.web.servlet.ModelAndView;
 
import com.appirio.jobs.domain.Job;
import com.appirio.jobs.domain.SmsMessage;
import com.mongodb.BasicDBObject;
import com.mongodb.DB;
import com.mongodb.DBCollection;
import com.mongodb.DBCursor;
import com.mongodb.Mongo;
import com.mongodb.MongoException;
import com.twilio.sdk.TwilioRestClient;
import com.twilio.sdk.TwilioRestException;
import com.twilio.sdk.TwilioRestResponse;
 
/**
 * @author Jeff Douglas (jeff@appirio.com)
 */
 
@RequestMapping("/job/**")
@Controller
public class JobController {
 
  private static final String ACCESS_TOKEN = "ACCESS_TOKEN";
  private static final String INSTANCE_URL = "INSTANCE_URL";
  private static Mongo m;
  private static DB db;
  private static DBCollection coll;
  private static DBCursor cur;
  private ArrayList<Job> jobs = new ArrayList<Job>();
 
 
    @RequestMapping(value="/job/list", method=RequestMethod.GET)
    public ModelAndView list(WebRequest req) {
 
      // if the job collection is empty then fetch jobs from Force.com
      if (jobs.isEmpty()) {
 
        // fetch the access token and url from the servlet session
        String accessToken = (String) req.getAttribute(ACCESS_TOKEN, RequestAttributes.SCOPE_SESSION);
        String instanceUrl = (String) req.getAttribute(INSTANCE_URL, RequestAttributes.SCOPE_SESSION);
 
        System.out.println("Access token: "+accessToken);
        System.out.println("Instance Url: "+instanceUrl);
 
        jobs = new ArrayList<Job>();
      HttpClient httpclient = new HttpClient();
          GetMethod gm = new GetMethod(instanceUrl + "/services/data/v20.0/query");
          //set the token in the header
          gm.setRequestHeader("Authorization", "OAuth "+accessToken);
          //set the SOQL as a query param
          NameValuePair[] params = new NameValuePair[1];
          //no need to url encode here...it will cause your query to fail
          params[0] = new NameValuePair("q","Select Id, Name, Job_Title__c, Location__c, " +
              "Duties__c, Skills__c, Salary__c, Box_Url__c from Job__c Order by Job_Title__c");
          gm.setQueryString(params);
 
          String respBody = "";
 
          try {
        httpclient.executeMethod(gm);
        respBody = gm.getResponseBodyAsString();
            System.out.println("response body: " + respBody);
      } catch (HttpException e1) {
        // TODO Auto-generated catch block
        e1.printStackTrace();
      } catch (IOException e2) {
        // TODO Auto-generated catch block
        e2.printStackTrace();
      } finally {
              gm.releaseConnection();
          }
 
          try {
              JSONObject json = new JSONObject(respBody);                
              JSONArray results = json.getJSONArray("records");
 
             for(int i = 0; i < results.length(); i++) {
               // add the json payload to a Job object
               Job job = new Job(results.getJSONObject(i).getString("Id"), 
            results.getJSONObject(i).getString("Name"),
            results.getJSONObject(i).getString("Job_Title__c"),
            results.getJSONObject(i).getString("Location__c"),
            results.getJSONObject(i).getString("Duties__c"),
            results.getJSONObject(i).getString("Skills__c"),
            results.getJSONObject(i).getString("Salary__c"),
            results.getJSONObject(i).getString("Box_Url__c"));
 
               // add the job to the collection
               jobs.add(job);
             }
 
 
          } catch (JSONException e) {
              e.printStackTrace();
          }
 
          System.out.println("jobs found: "+jobs.size());
 
      }
 
      ModelAndView mav = new ModelAndView("job/list");
      mav.addObject("jobs", jobs);
      return mav;
    }
 
    @RequestMapping(value="/job/{id}/display", method=RequestMethod.GET)
    public ModelAndView display(@PathVariable String id, Model model) {
      Job job = getJobById(id);
      incrementCount(job.getName(),"views");
      ModelAndView mav = new ModelAndView("job/display");
      mav.addObject(getJobById(id));
      return mav;
    }
 
    @RequestMapping(value="/job/{id}/sms", method=RequestMethod.GET)
    public ModelAndView message(@PathVariable String id, Model model) {
      ModelAndView mav = new ModelAndView("job/sms"); 
      SmsMessage sms = new SmsMessage();
      sms.setPhone("9412274843");
      sms.setMessage("Check out this AWESOME job with Appirio!");
      mav.addObject("smsMessage", sms);
      mav.addObject(getJobById(id));
      return mav;
    }
 
    @RequestMapping(value="/job/{id}/print", method=RequestMethod.GET)
    public String print(@PathVariable String id, Model model) {
      Job job = getJobById(id);
      incrementCount(job.getName(),"downloads");
      System.out.println(job.getBoxUrl());
      return "redirect:"+job.getBoxUrl();
    }
 
    @RequestMapping(value = "/job/{id}/smsSend", method = RequestMethod.POST)
    public ModelAndView smsSubmit(@PathVariable String id, @ModelAttribute SmsMessage sms, Model model) {
 
      Job job = getJobById(id);
      sendSms(job, sms.getPhone(), sms.getMessage());
      incrementCount(job.getName(),"messages");
 
      ModelAndView mav = new ModelAndView("job/smsConfirm"); 
      mav.addObject("phone", sms.getPhone());
      mav.addObject("message", sms.getMessage());
      mav.addObject(job);
      return mav;
 
    }
 
  private void incrementCount(String name, String type) {
 
    try {
      m = new Mongo("flame.mongohq.com", 27065);
      db = m.getDB("AppirioCareers");
      char[] password = { '4','+','r','E','o','x','x','x','x','x'};
      boolean auth = db.authenticate("jeffdonthemic", password);
      System.out.println("Mongo auth?: "+auth);
      coll = db.getCollection("jobs");  
    }
    catch (UnknownHostException ex) {
      ex.printStackTrace();
    }
    catch (MongoException ex) {
      ex.printStackTrace();
    }
 
    cur = coll.find(new BasicDBObject("name", name));  
    while (cur.hasNext()) {
      BasicDBObject doc = (BasicDBObject)cur.next();
      if (type.equals("views"))
        doc.put("views", (Integer)doc.get("views")+1);
      else if (type.equals("messages"))
        doc.put("messages", (Integer)doc.get("messages")+1);
      else
        doc.put("downloads", (Integer)doc.get("downloads")+1);
      coll.update( new BasicDBObject("name", name), doc );
    }
 
  }
 
    private void sendSms(Job job, String phone, String message) {
 
        String AccountSid = "YOUR-ACCOUNT-ID";
        String AuthToken = "YOUR-AUTH-TOKEN";
        String ApiVersion = "2010-04-01";
 
        TwilioRestClient client = new TwilioRestClient(AccountSid, AuthToken, null);
 
        String msg = "\n"+message+"\n"+job.getJobTitle()+"\nhttp://appirio.com/careers";
 
        System.out.println("size: "+msg.length());
 
        //build map of post parameters 
        Map<String,String> params = new HashMap<String,String>();
        params.put("From", "14155992671");
        params.put("To", phone);
        params.put("Body", msg);
        TwilioRestResponse response;
        try {
            response = client.request("/"+ApiVersion+"/Accounts/"+AccountSid+"/SMS/Messages", "POST", params);
 
            if(response.isError())
                System.out.println("Error making outgoing call: "+response.getHttpStatus()+"\n"+response.getResponseText());
            else {
                System.out.println(response.getResponseText());
 
            }
        } catch (TwilioRestException e) {
            e.printStackTrace();
        }
 
    }
 
    private Job getJobById(String id) {
      Job job = null;
      for (Job j : jobs) {
        if (j.getId().equals(id)) {
          job = j;
          break;
        }
      }
      return job;
    }
 
    @RequestMapping
    public String index() {
        return "job/index";
    }
 
}

 

]]> http://blog.jeffdouglas.com/2010/12/17/salesforce-rest-api-demo-from-cloudstock/feed/ 2 My VMforce and Facebook Demos Today at Dreamforce http://blog.jeffdouglas.com/2010/12/08/my-vmforce-and-facebook-demos-today-at-dreamforce/?utm_source=rss&utm_medium=rss&utm_campaign=my-vmforce-and-facebook-demos-today-at-dreamforce http://blog.jeffdouglas.com/2010/12/08/my-vmforce-and-facebook-demos-today-at-dreamforce/#comments Wed, 08 Dec 2010 15:28:40 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=3333

If you are at Dreamforce today here are the sessions that I am speaking in. I’m really excited to be part of both of them as the topics (VMforce and the new Facebook toolkit) are really cool.

Leveraging Public Social Networks – West 2005 @ 12:15

We’ll be showing off the new Facebook toolkit and building a few applications.

df10-facebook.png



VMforce: The Trusted Enterprise Platform as a Service - Force.com Theater @ 1:45

I’ll be demoing an app built using Spring STS, Spring Roo and Spring MVC connecting to the Force.com Database using JPA and running on the VMforce servers. I’ll show you the code, pick it apart and talk about best practices.

df10-vmforce.png

]]> http://blog.jeffdouglas.com/2010/12/08/my-vmforce-and-facebook-demos-today-at-dreamforce/feed/ 2 Cloud Computing for Java Developers Webinar (VMforce) http://blog.jeffdouglas.com/2010/09/10/cloud-computing-for-java-developers-webinar-vmforce/?utm_source=rss&utm_medium=rss&utm_campaign=cloud-computing-for-java-developers-webinar-vmforce http://blog.jeffdouglas.com/2010/09/10/cloud-computing-for-java-developers-webinar-vmforce/#comments Fri, 10 Sep 2010 09:46:00 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=3237

I attended the Cloud Computing for Java Developers webinar yesterday, which was essentially an intro to VMforce and the Force.com platform for (non-Force.com) Java developers. Quinton Wall and Jesper Joergensen did a good job with the overview of the platform but I was really looking for some tidbits on VMforce. You can watch the recording of the webinar but here are some things that I found interesting…

1. For accessing the Force.com Database, developers will be able to use JPA, the new REST API and the Force.com WSC (SOAP-based).

2. According to Jesper, VMforce will not be included for all orgs. It will be an additional cost possibly as an additional license or subscription. However, it will be available to developers in DE orgs.

3. The Force.com IDE installs on top of SpringSouce Tool Suite (Eclipse)

4. Quinton provided a little more info on the REST API that will be piloted starting Winter 11.

5. VMforce apps are built, tested and debugged locally and then deployed to the Force.com tcServer instance as easily as any other web application would be deployed on-premise. To the IDE, Force.com just looks like another server.

6. Quinton did a quick demo where he created a simple POJO, deployed it to the server and it automatically created a Custom Object for it in Force.com (this auto-generation will probably be configurable in the future). VMforce is using the JPA implementation from DataNucleus (same as App Engine). Quinton’s provided some code examples where he queried Contact records using JPA and then displayed them in the browser:

The summary slide wrapped up the webinar.

]]> http://blog.jeffdouglas.com/2010/09/10/cloud-computing-for-java-developers-webinar-vmforce/feed/ 2 Error Compiling Salesforce Metadata API with WSC http://blog.jeffdouglas.com/2010/07/01/error-compiling-salesforce-metadata-api-with-wsc/?utm_source=rss&utm_medium=rss&utm_campaign=error-compiling-salesforce-metadata-api-with-wsc http://blog.jeffdouglas.com/2010/07/01/error-compiling-salesforce-metadata-api-with-wsc/#comments Thu, 01 Jul 2010 12:00:52 +0000 Jeff Douglas http://blog.jeffdouglas.com/2010/07/01/error-compiling-salesforce-metadata-api-with-wsc/

This might not be relevant right now but you may find it useful in the near future. I’m tinkering with an app that spits out documentation for an org. I really hate doing documentation and am quite lazy so I thought I’d write something to allow my computer to do my work for me.

I ran into a small issue when trying to compile the Metadata WSDL with the Force.com Web Services Connector so I thought I’d post my fix.

So to use the Metadata API with the WSC, first download the Metadata WSDL from your org and the latest WSC jar from the project. Now issue something like the following to generate the stub code from the WSDL:

java -classpath wsc-19.jar com.sforce.ws.tools.wsdlc metadata.wsdl metadata.jar

Unfortunately this results in an error similar to:

-dir/com/sforce/soap/metadata/Encoding.java:12: ‘} ‘ expected UTF-8,


The error is thrown because the WSDL contains some hyphens that is making the compiler puke. You can fix the issue by replacing the hyphens in the Metadata WSDL with underscores, saving the WSDL and then compiling the stub code again.

Here’s the offending portion of the Metadata WSDL.


]]> http://blog.jeffdouglas.com/2010/07/01/error-compiling-salesforce-metadata-api-with-wsc/feed/ 3 Get Ready for VMForce – Here’s How! http://blog.jeffdouglas.com/2010/06/29/get-ready-for-vmforce/?utm_source=rss&utm_medium=rss&utm_campaign=get-ready-for-vmforce http://blog.jeffdouglas.com/2010/06/29/get-ready-for-vmforce/#comments Tue, 29 Jun 2010 14:59:41 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=2730

VMForce is coming (sometime in the near future) so what can you do to get started now? If I was a betting man (with inside info), here is what I’d do to get ready.

Start Building on Google App Engine
My guess is that VMForce will look a little like Google App Engine. You’ll probably have access to a wide range of Java libaries but not all of them. Based upon Salesforce.com’s current model you can expect that there will be some platform governors and limits in place. This should provide you with some experience and a working knowledge of some issues you may run into. If you want to get up and running quickly you can always buy my book Beginning Java Google App Engine (yes… blatant plug).

Start Learning Spring
I would probably start with Spring MVC or Spring Web Flow 2 initially. The good thing is that most of Spring also runs on App Engine so you should be able to move any apps you write on App Engine to VMForce. Here’s a great article to get you started with Spring MVC.

I would also download the SpringSource Tool Suite which is a Eclipse plugin for Spring development. It should fit in nicely with the Force.com IDE.

You might also want to dowload Spring’s tc Server Developer Edition. If you are using App Engine you can develop locally but you might also want to check out tc Server. The key component of tc Server Developer Edition is the Spring Insight console, a dashboard view of real-time Spring application performance metrics. Without changing code, developers can use Spring Insight to detect, analyze and diagnose application performance issues right from the desktops. This was demoed at Google IO and it was very slick! There’s a really cool video if you want to see how it works.

Dig into Persistence Layers
You’ll definitely want to start working with a persistance layer like JDO, JPA or Hibernate. Based upon some recent comments from Salesforce.com, I would look at JPA first.

Develop with the Force.com Web Service Connector (WSC)
Most developers are familiar with the WS-APIs but you should really start looking at the Force.com Web Service Connector. I’m writing an article for developer.force.com on how to use the WSC so keep an eye out for that shortly.

Try Spring Roo
If you have some extra time you might want to look into Spring Roo. Roo is a lightweight developer tool that allows you to build apps in minutes. They demoed Roo and Google Web Toolkit together at Google IO with impressive results.


]]> http://blog.jeffdouglas.com/2010/06/29/get-ready-for-vmforce/feed/ 6 Salesforce Chatter for Android http://blog.jeffdouglas.com/2010/06/06/salesforce-chatter-for-android/?utm_source=rss&utm_medium=rss&utm_campaign=salesforce-chatter-for-android http://blog.jeffdouglas.com/2010/06/06/salesforce-chatter-for-android/#comments Sun, 06 Jun 2010 15:25:23 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=2628

My blog has been a little quiet since I left for Google IO a few weeks ago and this is primarily the reason why. In addition to my day job I’ve been working on getting up-to-speed on Android development. Google sent me a Droid about a month before the conference and I started playing around with some tutorials and writing a few apps before IO (smart idea to send out 5K Droids to spur development). I really caught the Android bug at the event and thought that the Chatter Developer Challenge would be a great way to kill two birds with the proverbial one stone.

So here is the demo of the application that I just submitted for the Chatter Developer Challenge. It is a Salesforce Chatter for Android app running on a combination of the Force.com platform, Google App Engine and a Google Android mobile handset. It utilizes Force.com Remote Access Applications with 3-legged OAuth for security. The Android application has the following functionality:

  • Display your Chatter NewsFeed
  • Update your User status
  • Refresh your Chatter NewsFeed and store it in the local SQLite database
  • Choose a project (custom object) that you are following and view its Chatter Feed
  • Update the project’s status
  • Refresh the Chatter Feed for the project (including field changes to the record) and store it in the local SQLite database

The app does not include the functionality to reply to posts. Since Chatter is running in a Developer Edition and they are only allowed to have 1 user, it seemed rather pointless to respond to my own posts.

www.youtube.com/watch?v=2KggRjco6bs

Here are some screenshots of the application in case you want to skip the video.

I use Google App Engine to tie all of this applications together and provide a coherent security model. So I wrote a small App Engine app that uses OAuth to authorize access to Force.com and my Chatter feeds using Force.com Remote Access Application. Once authorized the Force.com Web Services Connector, running on App Engine, performs the interactions with SFDC such as submitting new status updates, fetching my feeds and displaying them as JSON objects.

App Engine recently started supporting 2-legged OAuth in combination with Google Accounts so that any App Engine application can become an OAuth service provider. Since OAuth support is baked into the Android platform I tried to hook up the Android handset as an OAuth consumer but could not finish in time to submit my entry to the Developer Challenge.


Since Android doesn’t play well with SOAP-based Web Services I think this approach in combination with JSON makes an appealing option. If you have any ideas, I’d love to hear them. I expect to write some more apps for Salesforce.com as the Android platform is fairly easy to grok. If you are familiar with using Eclipse with Force.com, App Engine, GWT or Java in general it seems much faster to get an app up and running with Android than with Objective-C for the iPhone. Just my $.02.


]]> http://blog.jeffdouglas.com/2010/06/06/salesforce-chatter-for-android/feed/ 4 WaveMaker’s IDE for the Cloud http://blog.jeffdouglas.com/2010/06/04/wavemakers-ide-for-the-cloud/?utm_source=rss&utm_medium=rss&utm_campaign=wavemakers-ide-for-the-cloud http://blog.jeffdouglas.com/2010/06/04/wavemakers-ide-for-the-cloud/#comments Fri, 04 Jun 2010 10:44:16 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=2620

Yesterday at Appirio we had a private demo of the WaveMaker platform from the guys at WaveMaker. I’ll try to recap most of the things that I heard as it pertains to Salesforce.com and vmforce but for more details you’ll want to check out their website.

The WaveMaker platform allows you to build applications that are portable across cloud environments. WaveMaker’s rapid application development platform consists of two products:

  • WaveMaker Studio: a visual, drag & drop development tool that runs in a browser and can be installed on a desktop or accessed via the cloud.
  • WaveMaker Server: a Java framework that provides security and data management, runs in any Java server and deploys on-site or in the cloud

The WaveMaker Studio is a pretty slick drag-n-drop interface with live previews of data for bound widgets. You can consume Web Services, database schemas and Java services to automatically generate boilerplate code for you. On the frontend it generates Dojo widgets and Spring and Hibernate components for the backend. It essentially spits out a standard Spring application that will run in any standard J2EE environment.

Development features include:

  • Drag & drop application assembly
  • One-click database import
  • One-click CRUD data forms
  • One-click related data forms
  • Live data preview within studio
  • Single sign-on security
  • Role-based access controls
  • Rich entry field validation
  • Built-in data grid pagination
  • Auto-complete search boxes

So how does this related to Salesforce.com? They are working for a release in July that supports the Force.com platform and will run on VMforce. They can consume the Enterprise WSDL and generate a standard front and back end components that you can import into Eclipse and start customizing. Their goal is to treat Salesforce just like any other database. However they are trying to build in some platform logic such as governor and limits based up the running edition. These java apps can then be deployed to EC2 and VMforce.


If you are interested, there is a free, community edition you can get started with right away. I’m not sure of the pricing for their enterprise or cloud editions so you’ll want to check with them if they have a seat and/or runtime license before you invest too much time.

Some other interesting points from yesterday’s meeting:

  • Web Fast: with WaveMaker’s visual tools, any developer can start building enterprise Java applications with minimal training.
  • CIO Safe: WaveMaker creates standard Java applications, boosting developer productivity and quality without compromising flexibility.
  • Cloud Ready: WaveMaker enables one-click deployment of rich internet applications to on-site or cloud hosting.
  • Cuts Java learning curve 92%: College grads can build Java web apps in 2 months versus 2 years
  • Reduces code 98%: Migrated .NET app with 26K lines of code to WaveMaker with 335 lines.
  • Slashes maintenance 75%: Self-service for call center app eliminates 75% of maintenance costs


]]> http://blog.jeffdouglas.com/2010/06/04/wavemakers-ide-for-the-cloud/feed/ 0 Java Command Line App Using the Salesforce WSC http://blog.jeffdouglas.com/2010/05/17/java-command-line-app-using-the-salesforce-wsc/?utm_source=rss&utm_medium=rss&utm_campaign=java-command-line-app-using-the-salesforce-wsc http://blog.jeffdouglas.com/2010/05/17/java-command-line-app-using-the-salesforce-wsc/#comments Mon, 17 May 2010 12:42:27 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=2545

The Force.com Web Service Connector (WSC) is a high performance web services stack that is much easier to implement than the “tried and true” Force.com Web Services API. Here’s a quick command line app you can use as a starter application. This class simply creates a new Account and then queries for the 5 newest Accounts by created date.

To get started, download wsc-18.jar from the WSC project’s download page to your desktop (any location will do). Now log into your Developer org and download the Partner WSDL (Setup -> App Setup -> Develop -> API) to your desktop as “partner.wsdl”. Now we’ll need to generate the stub code from the Partner WSDL. Make sure you have Java 1.6 installed and open a command prompt. Now run wsdlc on the Partner WSDL you just downloaded (detailed instruction are here):

java -classpath wsc-18.jar com.sforce.ws.tools.wsdlc partner.wsdl partner.jar

This will create a “partner.jar” file on your desktop. If you are using a Sandbox instead of a Developer or Production org, here are instructions for running wsdlc as there are a few issues. Your console should look similar to:

Note: You can also simply download the partner-18.jar and bypass the steps above to generate the partner.jar.

Now create a new Java project in Eclipse, add the wsc-18.jar and partner.jar files to your build path and copy the code below. You’ll need to add your username and password/security token before you run the code. Running the code should produce output similar to:

Here’s the starter code for the application.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

package com.jeffdouglas;
 
import com.sforce.soap.partner.*;
import com.sforce.soap.partner.sobject.*;
import com.sforce.ws.*;
 
public class Main {
 
  public static void main(String[] args) {
 
    ConnectorConfig config = new ConnectorConfig();
    config.setUsername("YOUR-USERNAME");
    config.setPassword("YOUR-PASSWORD-AND-SECURITYTOKEN");
 
    PartnerConnection connection = null;
 
    try {
 
      // create a connection object with the credentials
      connection = Connector.newConnection(config);
 
      // create a new account
      System.out.println("Creating a new Account...");
      SObject account = new SObject();
      account.setType("Account");
      account.setField("Name", "ACME Account 1");
      SaveResult[] results = connection.create(new SObject[] { account });
      System.out.println("Created Account: " + results[0].getId());
 
      // query for the 5 newest accounts
      System.out.println("Querying for the 5 newest Accounts...");
      QueryResult queryResults = connection.query("SELECT Id, Name from Account " +
          "ORDER BY CreatedDate DESC LIMIT 5");
      if (queryResults.getSize() > 0) {
        for (SObject s: queryResults.getRecords()) {
          System.out.println("Id: " + s.getField("Id") + " - Name: "+s.getField("Name"));
        }
      }
 
    } catch (ConnectionException e) {
      // TODO Auto-generated catch block
      e.printStackTrace();
    }
 
  }
 
}
]]> http://blog.jeffdouglas.com/2010/05/17/java-command-line-app-using-the-salesforce-wsc/feed/ 8 Integrate Chatter & Twitter on Google App Engine using OAuth http://blog.jeffdouglas.com/2010/03/17/integrate-chatter-twitter-on-google-app-engine-using-oauth/?utm_source=rss&utm_medium=rss&utm_campaign=integrate-chatter-twitter-on-google-app-engine-using-oauth http://blog.jeffdouglas.com/2010/03/17/integrate-chatter-twitter-on-google-app-engine-using-oauth/#comments Wed, 17 Mar 2010 11:37:01 +0000 Jeff Douglas http://blog.jeffdouglas.com/?p=2340

Cross-posted at the Appirio Tech Blog.

At Appirio we’ve been excited about Salesforce Chatter for quite a while. We firmly believe that Chatter has the potential to bridge the gap between enterprise applications and the way people work. We were luckily enough to receive special prerelease access to Chatter to develop our Social PS Enterprise for the Dreamforce ’09 Chatter Keynote and if you missed the demo at Dreamforce ’09 you can find it here.

Chatter is now in private beta for 100 companies and it is enabled in our production org. We’ve been using it for couple of weeks now and I find myself logging into our org more and more to check the status of other employees, projects and opportunities. As a developer I really wanted to get my hands on the code and test drive Chatter’s functionality. Luckily Quinton Wall has a great Intro to Chatter on developer.force.com to get me started. Sure, I could have developed an Apex and Visualforce application for Chatter but I naturally wanted to integrate Chatter with Twitter. So what I came up with is a Chatter/Twitter app running on Google App Engine using OAuth for Twitter authentication.

www.youtube.com/watch?v=FqeGxAuFqSM

Understanding Chatter

Initially I was under the assumption that Salesforce.com would release some sort of API for Chatter. However, they’ve done something even better. Instead of a new API to learn, Salesforce.com exposed Chatter as a series of sObjects allowing you to query for records using the same SOQL that you know and love and manipulate records using DML. Once you get a grip on the Chatter object model and where data lives, developing applications for Chatter is essentially the same as using the Sales or Service Could.


The Chatter model is based upon familiar social networking “Feed Posts”. These posts are made up of a series of Feed Items and Feed Types. The FeedPost stores most of the information that you are concerned about such as the body, title and any content related data. The FeedPost object also contains the information for all posts for the User object including profile statuses, news feeds and entity updates (accounts, contacts or custom objects). The Feed Types are dependent on what actions you are performing:

  • UserStatus - this is the user status update (e.g., “What are you working on?”)
  • TextPost - a post you make from a record
  • LinkPost - a post that contains a URL link (when you click on the link icon)
  • ContentPost - a post that contains some type of uploaded content such as a document or graphic
  • TrackedChanges - whenever a field on a record (set up during Chatter Feed Tracking configuration) is updated

One thing to understand from the beginning is that you do not query for Feed Posts directly. You must query via the Feed Item which contains a reference to the details of the post. So to get the last status update for the current user, you would issue the following SOQL:

SELECT Id, FeedPost.Body FROM UserFeed WHERE ParentId = :Userinfo.getUserId()
And Type = ‘UserStatus’ ORDER BY CreatedDate DESC LIMIT 1

For more sample Chatter code, check out the Chatter Code Recipes.

Functional Design

From a high-level overview, the application is fairly simple. When it initially loads the user is prompted to log into Twitter using OAuth.


Twitter asks you to grant the App Engine application the ability to access and update your Twitter account. I’m currently working on OAuth for Salesforce.com and hope to have both sides of the application using OAuth soon. Currently my Salesforce.com sandbox credentials are hard-coded in the application.


Once you authorize access you are redirected back to the application on Google App Engine and presented the following options:

  • Send your latest tweet to Chatter - fetches your last tweet from your timeline and sends it to Chatter as a status update.
  • Tweet your latest Chatter status update - queries for you last Chatter update and tweets it. Since Chatter is designed to be private within your org this option isn’t recommended for production and I only implemented it for academic purposes.
  • Send a status update to both Chatter and Twitter - presents you with a simple form to enter your status update. Once the form is submitted, your status is sent to both Chatter and Twitter.


Technical Design

The application is developed on Google App Engine using the Force.com Web Service Connector (WSC), Salesfore.com Partner library, and the Twitter4j Java library. Since we are using Google App Engine, download the wsc-gae-16_0.jar and partner-library.jar Jars from the WSC project. I used Chatter on one of our sandboxes so I had to do a little tweaking to get the Partner jar running. Now create a new Web Application Project for App Engine and then drop your two jars and the twitter4j jar into the lib directory. You’ll also need to add them to your project’s build path in Eclipse.

Next you’ll have to register your app with Twitter. This will give you the consumer key, consumer secret and URLs you’ll need to authenticate and make requests to Twitter. I’m storing these credentials along with the Salesforce.com sandbox credentials and user id as static variables in a simple credentials class for ease of use.

The
application is a series of JSPs and Servlets and if you’d like the code for the entire project, send me a message. The interesting parts of the application are described below and hopefully you can extrapolate the rest.

LoginServlet

This is the initial request for the application. The code uses the Twitter credentials and gets the authorization URL for the app and presents it to the users in the JSP page. The user clicks this link and is taken to Twitter to authorize the application.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

package com.jeffdouglas;
 
import java.io.IOException;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.http.*;
import org.apache.log4j.Logger;
import twitter4j.Twitter;
import twitter4j.TwitterException;
import twitter4j.TwitterFactory;
import twitter4j.http.RequestToken;
 
public class LoginServlet extends HttpServlet {
 
  private static final Logger log = Logger.getLogger(LoginServlet.class);
 
  public void doGet(HttpServletRequest req, HttpServletResponse resp)
      throws IOException {
 
    HttpSession session = req.getSession();
    Twitter twitter = new TwitterFactory().getInstance();
    twitter.setOAuthConsumer(Credentials.TWITTER_CONSUMERKEY,Credentials.TWITTER_CONSUMERSECRET);
    RequestToken requestToken = null;
 
    try {
      requestToken = twitter.getOAuthRequestToken();
    } catch (TwitterException e) {
      log.error(e.toString());
    }
 
    // get the token and tokenSecret
    String token = (String)requestToken.getToken();
    String tokenSecret = (String)requestToken.getTokenSecret();
    // store the token and tokenSecret in the session
    session.setAttribute("token", token);
    session.setAttribute("tokenSecret", tokenSecret);
 
    // get the url that the user must click to authenticate w/OAuth
    String authUrl = requestToken.getAuthorizationURL();
    req.setAttribute("authUrl", authUrl);
    RequestDispatcher rd = req.getRequestDispatcher("login.jsp");
 
    try {
      rd.forward(req, resp);
    } catch (ServletException e) {
      log.error(e.toString());
    }
 
  }
}

SendChatterServlet

This Servlet runs when the user clicks the Twitter -> Chatter link. The code grabs the user’s last tweet and the uses the Partner Web Services API to submit the sObject with the new Chatter status to Salesforce.com.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108

package com.jeffdouglas;
 
import java.io.IOException;
import java.util.List;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import org.apache.log4j.Logger;
import twitter4j.Status;
import twitter4j.Twitter;
import twitter4j.TwitterException;
import twitter4j.TwitterFactory;
import twitter4j.http.AccessToken;
 
import com.sforce.ws.*;
import com.sforce.soap.partner.*;
import com.sforce.soap.partner.sobject.SObject;
 
public class SendChatterServlet extends HttpServlet {
 
  private static final Logger log = Logger.getLogger(SendTweetServlet.class);
 
  public void doGet(HttpServletRequest req, HttpServletResponse resp)
  throws IOException {
 
    PartnerConnection connection = null;
    // get the user's last tweet
    String tweet = getLastTweet(req,resp);
 
    if (tweet != null) {
 
      try {
        if (connection == null) {
          ConnectorConfig config = new ConnectorConfig();
          config.setUsername(Credentials.SFDC_USERNAME);
          config.setPassword(Credentials.SFDC_PASSWORD);
          connection = Connector.newConnection(config);
        }
 
        // create the sobject to hold the post
        SObject post = new SObject();
        post.setType("FeedPost");
        post.setField("ParentId", Credentials.SFDC_USERID);
        post.setField("Body", tweet);
        // submit the update to Salesforce.com
        connection.create(new SObject[]{post});
 
      } catch (ConnectionException ce) {
        log.error(ce.toString());
      }
 
      resp.getWriter().println("Tweet sent to Chatter: "+tweet);
    } else {
      resp.getWriter().println("Could not fetch the lastes update from Twitter. Nothing sent to Chatter.");
    }
 
  }
 
  private String getLastTweet(HttpServletRequest req, HttpServletResponse resp) {
 
    String tweet = null;
    HttpSession session = req.getSession();
    Twitter twitter = new TwitterFactory().getInstance();
 
    twitter.setOAuthConsumer(Credentials.TWITTER_CONSUMERKEY,
        Credentials.TWITTER_CONSUMERSECRET);
 
    // if the access token is present in the session
    if (session.getAttribute("accessToken") == null){
        // get the request token from the session
        String token = (String) session.getAttribute("token");
        String tokenSecret = (String)session.getAttribute("tokenSecret");
 
        // get the access token from twitter
        AccessToken accessToken = null;
        try {
          accessToken = twitter.getOAuthAccessToken(token, tokenSecret);
        } catch (TwitterException e) {
          log.error(e.toString());
        }
        twitter.setOAuthAccessToken(accessToken);
 
        // save the access token, that are different from request token
        session.setAttribute("accessToken", accessToken.getToken());
        session.setAttribute("accessTokenSecret", accessToken.getTokenSecret());
 
    } else {
        // use the access token from the session
        twitter.setOAuthAccessToken((String)session.getAttribute("accessToken"),
            (String)session.getAttribute("accessTokenSecret"));
    }
 
    List<status> statuses = null;
    try {
      // get the user's timeline
      statuses = twitter.getUserTimeline();
      // set their last tweet to return
      tweet = statuses.get(0).getText();
    } catch (TwitterException e) {
      log.error(e.toString());
    }
 
    return tweet;
 
  }
 
}

SendTweetServlet

When the user clicks the Chatter -> Twitter link, this Servlet queries Salesforce.com for the user’s most recent status update, finds the status in the returned XML results and then sends the status out as a tweet.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120

package com.jeffdouglas;
 
import java.io.IOException;
import java.util.Iterator;
import javax.servlet.http.*;
import org.apache.log4j.Logger;
import twitter4j.Twitter;
import twitter4j.TwitterException;
import twitter4j.TwitterFactory;
import twitter4j.http.AccessToken;
 
import com.sforce.ws.*;
import com.sforce.ws.bind.XmlObject;
import com.sforce.soap.partner.*;
import com.sforce.soap.partner.sobject.SObject;
 
public class SendTweetServlet extends HttpServlet {
 
  private static final Logger log = Logger.getLogger(SendTweetServlet.class);
 
  public void doGet(HttpServletRequest req, HttpServletResponse resp)
      throws IOException {
 
    PartnerConnection connection = null;
    String feedPost = null;
 
    try {
      if (connection == null) {
        ConnectorConfig config = new ConnectorConfig();
        config.setUsername(Credentials.SFDC_USERNAME);
        config.setPassword(Credentials.SFDC_PASSWORD);
        connection = Connector.newConnection(config);
      }
 
      QueryResult results = connection
          .query("SELECT Id, FeedPost.Body FROM UserFeed WHERE "
              + "ParentId = '" + Credentials.SFDC_USERID + "'"
              + " And Type = 'UserStatus' ORDER BY CreatedDate DESC LIMIT 1");
 
      // in this case there will only be 1 record returned, but....
      for (int i = 0; i < results.getRecords().length; i++) {
        SObject feed = results.getRecords()[i];
        feedPost = getFeedBody(feed);
      }
 
    } catch (ConnectionException ce) {
      log.error(ce.toString());
    }
 
    if (feedPost != null) {
      sendTweet(feedPost, req, resp);
      resp.getWriter().println("Chatter message sent to Twitter: " + feedPost);
    } else {
      resp.getWriter().println("Nothing sent to Twitter");
    }
 
  }
 
  private void sendTweet(String tweet, HttpServletRequest req, HttpServletResponse resp) {
 
    HttpSession session = req.getSession();
    Twitter twitter = new TwitterFactory().getInstance();
 
    twitter.setOAuthConsumer(Credentials.TWITTER_CONSUMERKEY,
        Credentials.TWITTER_CONSUMERSECRET);
 
    // if the access token is present in the session
    if (session.getAttribute("accessToken") == null){
        // get the request token from the session
        String token = (String) session.getAttribute("token");
        String tokenSecret = (String)session.getAttribute("tokenSecret");
 
        // get the access token from twitter
        AccessToken accessToken = null;
        try {
          accessToken = twitter.getOAuthAccessToken(token, tokenSecret);
        } catch (TwitterException e) {
          log.error(e.toString());
        }
        twitter.setOAuthAccessToken(accessToken);
 
        // save the access token, that are different from request token
        session.setAttribute("accessToken", accessToken.getToken());
        session.setAttribute("accessTokenSecret", accessToken.getTokenSecret());
 
    } else {
        // use the access token from the session
        twitter.setOAuthAccessToken((String)session.getAttribute("accessToken"),
            (String)session.getAttribute("accessTokenSecret"));
    }
 
    try {
      // update the user's twitter status
      twitter.updateStatus(tweet);
    } catch (TwitterException e) {
      log.error(e.toString());
    }
 
  }
 
  private String getFeedBody(SObject feed) {
    String feedBody = "";
    Iterator<xmlObject> feedPost = feed.getChildren();
    while (feedPost.hasNext()) {
      XmlObject post = feedPost.next();
      if (post.getValue() == null) {
        Iterator<xmlObject> body = post.getChildren();
        while (body.hasNext()) {
          XmlObject child = body.next();
          if (child.getName().toString().equals(
              "{urn:sobject.partner.soap.sforce.com}Body")) {
            feedBody = child.getValue().toString();
            break;
          }
        }
      }
    }
    return feedBody;
  }
}

SendBothServlet

This Servlet loads the HTML form presenting the user with a textbox to enter their new status. When the form is posted, the status is sent out to both Chatter and Twitter.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116

package com.jeffdouglas;
 
import java.io.IOException;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import org.apache.log4j.Logger;
import twitter4j.Twitter;
import twitter4j.TwitterException;
import twitter4j.TwitterFactory;
import twitter4j.http.AccessToken;
 
import com.sforce.soap.partner.Connector;
import com.sforce.soap.partner.PartnerConnection;
import com.sforce.soap.partner.sobject.SObject;
import com.sforce.ws.ConnectionException;
import com.sforce.ws.ConnectorConfig;
 
public class SendBothServlet extends HttpServlet {
 
  private static final Logger log = Logger.getLogger(SendTweetServlet.class);
 
  private void sendToChatter(String status) {
 
    PartnerConnection connection = null;
 
      try {
        if (connection == null) {
          ConnectorConfig config = new ConnectorConfig();
          config.setUsername(Credentials.SFDC_USERNAME);
          config.setPassword(Credentials.SFDC_PASSWORD);
          connection = Connector.newConnection(config);
        }
 
        // create the sobject to hold the post
        SObject post = new SObject();
        post.setType("FeedPost");
        post.setField("ParentId", Credentials.SFDC_USERID);
        post.setField("Body", status);
        // submit the update to Salesforce.com
        connection.create(new SObject[]{post});
 
      } catch (ConnectionException ce) {
        log.error(ce.toString());
      }
 
  }
 
  private void sendToTwitter(String status, HttpServletRequest req) {
 
    HttpSession session = req.getSession();
    Twitter twitter = new TwitterFactory().getInstance();
 
    twitter.setOAuthConsumer(Credentials.TWITTER_CONSUMERKEY,
        Credentials.TWITTER_CONSUMERSECRET);
 
    // if the access token is present in the session
    if (session.getAttribute("accessToken") == null){
        // get the request token from the session
        String token = (String) session.getAttribute("token");
        String tokenSecret = (String)session.getAttribute("tokenSecret");
 
        // get the access token from twitter
        AccessToken accessToken = null;
        try {
          accessToken = twitter.getOAuthAccessToken(token, tokenSecret);
        } catch (TwitterException e) {
          log.error(e.toString());
        }
        twitter.setOAuthAccessToken(accessToken);
 
        // save the access token, that are different from request token
        session.setAttribute("accessToken", accessToken.getToken());
        session.setAttribute("accessTokenSecret", accessToken.getTokenSecret());
 
    } else {
        // use the access token from the session
        twitter.setOAuthAccessToken((String)session.getAttribute("accessToken"),
            (String)session.getAttribute("accessTokenSecret"));
    }
 
    try {
      // update the user's twitter status
      twitter.updateStatus(status);
    } catch (TwitterException e) {
      log.error(e.toString());
    }
 
  }
 
  public void doPost(HttpServletRequest req, HttpServletResponse resp)
  throws IOException {
 
    sendToChatter(req.getParameter("status"));
    sendToTwitter(req.getParameter("status"),req);
 
    resp.getWriter().println("Sent the following to both Chatter and Twitter: "+req.getParameter("status"));
 
  }
 
  public void doGet(HttpServletRequest req, HttpServletResponse resp)
  throws IOException {
 
    try {
      RequestDispatcher rd = req.getRequestDispatcher("post.jsp");
      rd.forward(req, resp);
    } catch (ServletException e) {
      log.error(e.toString());
    }
 
  }
 
}


]]> http://blog.jeffdouglas.com/2010/03/17/integrate-chatter-twitter-on-google-app-engine-using-oauth/feed/ 0