Sri Lanka - Ambassador reports Sri Lankan President responsible for "alleged war crimes"
WikiLeaks Staff, 1 December 2010, 19.00 GMT
Sri Lankan President Mahinda Rajapaksa and his family are responsible for alleged war crimes against the Tamil, according to a cable sent by US ambassador to Sri Lanka Patricia Butenis.
Butenis said complicity in alleged war crimes by the president and leader of the opposition was stalling progress in launching investigations into the country’s civil war.
The long running conflict between the government of Sri Lanka and the LTTE, also known as the Tamil Tigers, was ended in May 2009 after the Sri Lankan army defeated LTTE leaders in an area known as the “no fire zone”.
The cable, dated 15 January 2010, updated the Secretary of State on war crimes accountability following the end of the country’s long and bloody conflict.
Ambassador Butenis noted there had been some limited progress in investigating potential war crimes, but noted:
“There are no examples we know of a regime undertaking wholesale investigations of its own troops or senior officials for war crimes while that regime or government remained in power.
“In Sri Lanka this is further complicated by the fact that responsibility for many of the alleged crimes rests with the country’s senior civilian and military leadership, including President Rajapaksa and his brothers and opposition candidate General Fonseka.”
With regard to alleged LTTE war crimes, Butenis noted:
“Most of the LTTE leadership was killed at the end of the war, leaving few to be held responsible for those crimes. The Government of Sri Lanka (GSL) is holding thousands of mid- and lower-level ex-LTTE combatants for future rehabilitation and/or criminal prosecution. It is unclear whether any such prosecutions will meet international standards.”
The revelations coincide with a visit by President Rajapaksa to the United Kingdom. Rajapaksa, who has been in the UK since Monday, is due to meet with UK Defence Secretary Liam Fox.
Rajapaksa was also scheduled to speak at the Oxford Union on Thursday until the university issued a statement cancelling the event on Wednesday afternoon. The statement cited “security concerns” due to the large number of protestors expected to picket the event.
Friday, January 28, 2011
That's because the cover letters I see usually fall into one of three categories:
The recap: The résumé in prose form. It's redundant, harder to read than the résumé, and provides no additional insight.
The form letter: This says, essentially, "Dear Sir or Madam: I saw your ad in the paper and thought you might like me." And it's clearly a form letter where maybe they got my name and company right. If they're lucky, I will still take the time to read their résumé after being insulted with a form letter.
The "I'm crazy": This one's rare, and it expands on the résumé of experience with some personal insights. Examples range from the merely batty ("I find batik as an art form has taught me to become both a better person and project manager.") to the truly terrifying ("I cast a pentagram hex and the central line pointed towards your job listing. I know you will find this as comforting as I do.")
There are really only a few times to use a cover letter:
When you know the name of the person hiring
When you know something about the job requirement
When you've been personally referred (which might include 1 and 2)
Under those conditions, you can help your cause by doing some of the résumé analysis for your potential new boss. To illustrate, here's the best cover letter I ever received:
Dear David:
I am writing in response to the opening for xxxx, which I believe may report to you.
I can offer you seven years of experience managing communications for top-tier xxxx firms, excellent project-management skills, and a great eye for detail, all of which should make me an ideal candidate for this opening.
I have attached my résumé for your review and would welcome the chance to speak with you sometime.
Best regards,
Xxxx Xxxx
Here's what I like about this cover letter: It's short. It sums up the résumé as it relates to the job. It asks for the job.
The writer of this letter took the time to think through what would be relevant to me. Instead of scattering lots of facts in hopes that one was relevant, the candidate offered up an opinion as to which experiences I should focus on.
And that means the writer isn't just showing me skills related to the job, he's showing me he'll be the kind of employee who offers up solutions — instead of just laying problems on my desk.
What do you think? Have you ever secured a job thanks to a cover letter? What's your view on the value — or lack thereof — of cover letters?
The recap: The résumé in prose form. It's redundant, harder to read than the résumé, and provides no additional insight.
The form letter: This says, essentially, "Dear Sir or Madam: I saw your ad in the paper and thought you might like me." And it's clearly a form letter where maybe they got my name and company right. If they're lucky, I will still take the time to read their résumé after being insulted with a form letter.
The "I'm crazy": This one's rare, and it expands on the résumé of experience with some personal insights. Examples range from the merely batty ("I find batik as an art form has taught me to become both a better person and project manager.") to the truly terrifying ("I cast a pentagram hex and the central line pointed towards your job listing. I know you will find this as comforting as I do.")
There are really only a few times to use a cover letter:
When you know the name of the person hiring
When you know something about the job requirement
When you've been personally referred (which might include 1 and 2)
Under those conditions, you can help your cause by doing some of the résumé analysis for your potential new boss. To illustrate, here's the best cover letter I ever received:
Dear David:
I am writing in response to the opening for xxxx, which I believe may report to you.
I can offer you seven years of experience managing communications for top-tier xxxx firms, excellent project-management skills, and a great eye for detail, all of which should make me an ideal candidate for this opening.
I have attached my résumé for your review and would welcome the chance to speak with you sometime.
Best regards,
Xxxx Xxxx
Here's what I like about this cover letter: It's short. It sums up the résumé as it relates to the job. It asks for the job.
The writer of this letter took the time to think through what would be relevant to me. Instead of scattering lots of facts in hopes that one was relevant, the candidate offered up an opinion as to which experiences I should focus on.
And that means the writer isn't just showing me skills related to the job, he's showing me he'll be the kind of employee who offers up solutions — instead of just laying problems on my desk.
What do you think? Have you ever secured a job thanks to a cover letter? What's your view on the value — or lack thereof — of cover letters?
Thursday, January 27, 2011
Friend --
Tonight I addressed the American people on the future we face together.
Though at times it may seem uncertain, it is a future that is ours to decide, ours to define, and ours to win.
I know we will.
Because, after the worst recession in decades, we see an economy growing again.
Because, after two years of job losses, we've added private-sector jobs for 12 straight months -- more than 1 million in all.
Because, time after time, when our resolve has been tested, we, as a nation, have always prevailed.
Overcoming the challenges we face today requires a new vision for tomorrow. We will move forward together, or not at all -- for the challenges we face are bigger than party, and bigger than politics.
Yet the story of America is this: We do big things.
Just as the progress of the past two years would not have been possible without your hard work, we will not realize the agenda I described tonight without you.
So as we continue this great mission together, and we set out the plans for how far we can go, I need to know that you are ready to work side by side with me once more.
Will you stand with me as we strive to win the future?
The last two years have been marked by unprecedented reforms and historic progress.
But there is much more work to do.
Moving forward, America's economic growth at home is inextricably connected to our competitiveness in the global community. The more products American companies can export, the more jobs we can create at home.
This vision for the future starts with innovation, tapping into the creativity and imagination of our people to create the jobs and industries of the future. Instead of subsidizing yesterday's energy, let's invest in tomorrow's. It's why I challenged Congress to join me in setting a new goal: By 2035, 80 percent of America's electricity will come from clean energy sources.
It means leading the world in educating our kids, giving each of our children the best opportunity to succeed and preparing them for the jobs of tomorrow.
We must build a 21st century infrastructure for our country, putting millions of Americans to work rebuilding roads and bridges and expanding high-speed Internet and high-speed rail.
We must reform government, making it leaner, smarter, and more transparent.
And we must take responsibility for our shared debt, reining in our long-term deficit so we can afford the investments we need to move our country forward.
That is the vision I laid out tonight. That is how we win the future.
It is going to take a lot of work -- but I have no doubt we are up to the task.
Half a century ago, when the Soviets beat us into space with the launch of a satellite called Sputnik, we had no idea how we'd beat them to the moon. The science wasn't there yet. NASA didn't even exist.
But after investing in better research and education, we didn't just surpass the Soviets. We unleashed a wave of innovation that created new industries and millions of new jobs.
This is our generation's Sputnik moment.
Please stand together with me:
http://my.barackobama.com/WintheFuture
It is because of each of you, who define the will of a people, that the state of our union is strong in the face of tough challenges. You are the reason our future is still bright in the face of deep uncertainty.
And you are the reason I believe that future is ours to win.
Thank you,
Barack
Tonight I addressed the American people on the future we face together.
Though at times it may seem uncertain, it is a future that is ours to decide, ours to define, and ours to win.
I know we will.
Because, after the worst recession in decades, we see an economy growing again.
Because, after two years of job losses, we've added private-sector jobs for 12 straight months -- more than 1 million in all.
Because, time after time, when our resolve has been tested, we, as a nation, have always prevailed.
Overcoming the challenges we face today requires a new vision for tomorrow. We will move forward together, or not at all -- for the challenges we face are bigger than party, and bigger than politics.
Yet the story of America is this: We do big things.
Just as the progress of the past two years would not have been possible without your hard work, we will not realize the agenda I described tonight without you.
So as we continue this great mission together, and we set out the plans for how far we can go, I need to know that you are ready to work side by side with me once more.
Will you stand with me as we strive to win the future?
The last two years have been marked by unprecedented reforms and historic progress.
But there is much more work to do.
Moving forward, America's economic growth at home is inextricably connected to our competitiveness in the global community. The more products American companies can export, the more jobs we can create at home.
This vision for the future starts with innovation, tapping into the creativity and imagination of our people to create the jobs and industries of the future. Instead of subsidizing yesterday's energy, let's invest in tomorrow's. It's why I challenged Congress to join me in setting a new goal: By 2035, 80 percent of America's electricity will come from clean energy sources.
It means leading the world in educating our kids, giving each of our children the best opportunity to succeed and preparing them for the jobs of tomorrow.
We must build a 21st century infrastructure for our country, putting millions of Americans to work rebuilding roads and bridges and expanding high-speed Internet and high-speed rail.
We must reform government, making it leaner, smarter, and more transparent.
And we must take responsibility for our shared debt, reining in our long-term deficit so we can afford the investments we need to move our country forward.
That is the vision I laid out tonight. That is how we win the future.
It is going to take a lot of work -- but I have no doubt we are up to the task.
Half a century ago, when the Soviets beat us into space with the launch of a satellite called Sputnik, we had no idea how we'd beat them to the moon. The science wasn't there yet. NASA didn't even exist.
But after investing in better research and education, we didn't just surpass the Soviets. We unleashed a wave of innovation that created new industries and millions of new jobs.
This is our generation's Sputnik moment.
Please stand together with me:
http://my.barackobama.com/WintheFuture
It is because of each of you, who define the will of a people, that the state of our union is strong in the face of tough challenges. You are the reason our future is still bright in the face of deep uncertainty.
And you are the reason I believe that future is ours to win.
Thank you,
Barack
'The Social Network' nominated for eight Oscars
The claim by Facebook co-founder Eduardo Saverin that he was unduly ousted from the social network's early executive team formed the basis for "The Social Network," the controversial yet acclaimed film about the birth of the company. Perhaps with a touch of unintended irony, when nominations for the 83rd Academy Awards were announced this morning, the actor who played Saverin was snubbed.
"The Social Network" netted eight nominations for the 83rd Academy Awards. Among them was the coveted Best Picture category--but actor Andrew Garfield, expected to be a shoo-in nomination and even a favorite to win Best Supporting Actor for his portrayal of Saverin, was left off the list.
Garfield's co-star Jesse Eisenberg was nominated for a Best Actor Oscar for playing Facebook CEO Mark Zuckerberg; director David Fincher was nominated for Best Director; and the screenplay by Aaron Sorkin was nominated for Best Screenplay Adaptation. The film was also nominated for Best Cinematography, Best Film Editing, Best Sound Mixing, and Best Original Score for its music by Nine Inch Nails' Trent Reznor and collaborator Atticus Ross.
In the Best Picture category, "The Social Network" will go up against "Black Swan," "The Fighter," "Inception," "The Kids Are All Right," "The King's Speech," "127 Hours," "Toy Story 3," "True Grit," and "Winter's Bone." Though not a heavy favorite to win, it does have a good shot.
But Eisenberg will have a tougher uphill battle in the Best Actor category. He'll go up against some heavy hitters, like Javier Bardem in "Biutiful" and Jeff Bridges in "True Grit," as well as acclaimed performances from Colin Firth in "The King's Speech" and fellow young actor James Franco in "127 Hours."
Despite being one of the most talked-about and well-received movies of the year, "The Social Network" did not lead the pack in the number of nominations announced today by the Academy of Motion Picture Arts and Sciences. "The King's Speech," a drama starring Colin Firth, was in first place with 12 total nominations, and Ethan and Joel Coen's remake of classic western "True Grit" followed with 10. "The Social Network" was tied for third place alongside the Christopher Nolan-directed "Inception."
Earlier this month, "The Social Network" won a Golden Globe award for best drama.
Read more: http://news.cnet.com/8301-13577_3-20029434-36.html#ixzz1CCczfWNI
The claim by Facebook co-founder Eduardo Saverin that he was unduly ousted from the social network's early executive team formed the basis for "The Social Network," the controversial yet acclaimed film about the birth of the company. Perhaps with a touch of unintended irony, when nominations for the 83rd Academy Awards were announced this morning, the actor who played Saverin was snubbed.
"The Social Network" netted eight nominations for the 83rd Academy Awards. Among them was the coveted Best Picture category--but actor Andrew Garfield, expected to be a shoo-in nomination and even a favorite to win Best Supporting Actor for his portrayal of Saverin, was left off the list.
Garfield's co-star Jesse Eisenberg was nominated for a Best Actor Oscar for playing Facebook CEO Mark Zuckerberg; director David Fincher was nominated for Best Director; and the screenplay by Aaron Sorkin was nominated for Best Screenplay Adaptation. The film was also nominated for Best Cinematography, Best Film Editing, Best Sound Mixing, and Best Original Score for its music by Nine Inch Nails' Trent Reznor and collaborator Atticus Ross.
In the Best Picture category, "The Social Network" will go up against "Black Swan," "The Fighter," "Inception," "The Kids Are All Right," "The King's Speech," "127 Hours," "Toy Story 3," "True Grit," and "Winter's Bone." Though not a heavy favorite to win, it does have a good shot.
But Eisenberg will have a tougher uphill battle in the Best Actor category. He'll go up against some heavy hitters, like Javier Bardem in "Biutiful" and Jeff Bridges in "True Grit," as well as acclaimed performances from Colin Firth in "The King's Speech" and fellow young actor James Franco in "127 Hours."
Despite being one of the most talked-about and well-received movies of the year, "The Social Network" did not lead the pack in the number of nominations announced today by the Academy of Motion Picture Arts and Sciences. "The King's Speech," a drama starring Colin Firth, was in first place with 12 total nominations, and Ethan and Joel Coen's remake of classic western "True Grit" followed with 10. "The Social Network" was tied for third place alongside the Christopher Nolan-directed "Inception."
Earlier this month, "The Social Network" won a Golden Globe award for best drama.
Read more: http://news.cnet.com/8301-13577_3-20029434-36.html#ixzz1CCczfWNI
Monday, January 24, 2011
Earth ‘to get a second sun’
on January 24th, 2011
The Earth could soon have a second sun, at least for a week or two.
The cosmic phenomenon will happen when one of the brightest stars in the night sky explodes into a supernova.
And, according to a report, the most stunning light show in the planet’s history could happen as soon as this year.
Earth will undoubtedly have a front row seat when the dying red super-giant star Betelgeuse finally blows itself into oblivion, the Daily Mail quoting the Australian website news.com.au. reports.
The explosion will be so bright that even though the star in the Orion constellation is 640 light years away, it will still turn night into day and appear like there are two suns in the sky for a few weeks. The only real debate is over exactly when it will happen.
In stellar terms, Betelgeuse is predicted to crash and burn in the near future. But that doesn’t necessarily mean you have to rush out and buy sunglasses.
Brad Carter, Senior Lecturer of Physics at the University of Southern Queensland in Australia, claimed Saturday that the galactic blast could happen before 2012 or any time over the next million years.
“This old star is running out of fuel in its centre,” Carter told news.com.au.
“This fuel keeps Betelgeuse shining and supported. When this fuel runs out, the star will literally collapse in upon itself and it will do so very quickly.
on January 24th, 2011
The Earth could soon have a second sun, at least for a week or two.
The cosmic phenomenon will happen when one of the brightest stars in the night sky explodes into a supernova.
And, according to a report, the most stunning light show in the planet’s history could happen as soon as this year.
Earth will undoubtedly have a front row seat when the dying red super-giant star Betelgeuse finally blows itself into oblivion, the Daily Mail quoting the Australian website news.com.au. reports.
The explosion will be so bright that even though the star in the Orion constellation is 640 light years away, it will still turn night into day and appear like there are two suns in the sky for a few weeks. The only real debate is over exactly when it will happen.
In stellar terms, Betelgeuse is predicted to crash and burn in the near future. But that doesn’t necessarily mean you have to rush out and buy sunglasses.
Brad Carter, Senior Lecturer of Physics at the University of Southern Queensland in Australia, claimed Saturday that the galactic blast could happen before 2012 or any time over the next million years.
“This old star is running out of fuel in its centre,” Carter told news.com.au.
“This fuel keeps Betelgeuse shining and supported. When this fuel runs out, the star will literally collapse in upon itself and it will do so very quickly.
Getting started with Galileo
Before you begin developing your Facebook SimpleRestaurantSearch application, you need to download and install the Galileo package of Eclipse (see Resources). In this section, you'll learn how to set it up.
Downloading Galileo
The Galileo package represents the next incremental release for Eclipse, and as such, means a new installation of the Eclipse platform. As with all Eclipse releases, there are a number of packages to choose from, depending upon your development needs.
Download the Eclipse IDE for Java™ EE Developers version, as it has everything you need to develop and deploy a Facebook application. Choose the version for your operating system, select an appropriate mirror, and download it (see Resources). The file is quite large — close to 190 MB depending on your platform — so be patient.
The Eclipse Web site provides a comparison chart, shown in Figure 1.
Figure 1. Package comparison chart
When the download is complete, unzip the package where you want Eclipse to be installed, then double-click the Eclipse icon to run it. Select a workspace, and Eclipse will take you to the welcome page. From here, choose the Workbench icon (the arrow on the far right of the welcome screen shown in Figure 2).
Figure 2. Eclipse Welcome screen
Setting up Tomcat in Eclipse
Eclipse Galileo allows you to integrate variety of servers so that any Web applications can be developed, debugged, and deployed. For the current Facebook SimpleRestaurantSearch application, you would use Tomcat as the application server (see Resources). Download Tomcat to a local folder and extract it.
Switch to Eclipse and open the server view (see Figure 3).
Figure 3. Server view in Eclipse
Right-click on the server view and select New > Server menu option (see Figure 4).
Figure 4. New server menu option
Define a new server by selecting the appropriate options. Select the Tomcat V6 Server option under Apache category. You can name the server as anything meaningful for the application like EclipseBook-Host, then click Next (see Figure 5).
Figure 5. Defining a new server
In the next wizard window, enter the Tomcat installation directory, select the required JRE, then click Finish (see Figure 6).
Figure 6. Setting the installation directory
Once Tomcat is properly configured, the server appears in the server view. By default, the server port is set to 8080 (see Figure 7).
Figure 7. Server appears in the server view
Next, we'll set up the Dynamic Web Project so you can work with your application's Web interface from within Eclipse.
Setting up the Dynamic Web Project
Click on the Project Explorer, and right-click and select the Dynamic Web Project (see Figure 8).
Figure 8. Setting up the Dynamic Web Project
Give the project a name and set the target runtime to be the Tomcat Server name. Remember that you name the Tomcat Server as EclipseBook-Host. Click Finish to create the Web project configured to use the Tomcat server and default Web configuration (see Figure 9).
Figure 9. Creating the Web project
Back to top
Downloading and setting up the Facebook Java API
As of May 2008, Facebook has discontinued any support of its official Java client, directing users interested developing Facebook applications in Java technology to use one of the various third-party clients out there. One of the popular Facebook Java APIs is available on Google (see Resources). As such, the purpose of this project is now to maintain, support, and extend the abandoned code base to provide a high-quality, up-to-date version of the Facebook API client for Java developers (see Figure 10).
Figure 10. Facebook Java API
Download the latest Java Facebook API (V3.0.0) into the local folder and extract the files (see Figure 11).
Figure 11. Downloading the latest Facebook Java API
The Facebook Java API contains all the libraries related to the Facebook Application API and other dependent JARs (see Figure 12). See Download for the source code of our sample application. Note that the JAR files aren't included in that ZIP file, since you download them here with the Facebook Java API.
Figure 12. Libraries related to the Facebook Application API and other dependent JARs
Copy all the Facebook Java Client JARs to the lib folder of the SimpleRestaurantSearch application. This will now enable the project to use the Facebook APIs (see Figure 13).
Figure 13. Copy all the Facebook Java Client JARs to lib folder
Back to top
Creating a Facebook application
Almost everyone has a presence on Facebook, including Web developers, business managers, and social geeks. Creating applications on the Facebook platform that leverage the Facebook Application API opens a window of visibility for users of all stripes, whether they wish to advertise a product or service or simply share information with friends.
To create a Facebook application, you first need to obtain a Facebook Platform API key. Follow these steps to create an application with the Facebook Developer application.
Go to the Get Started site to get an overview of the steps for setting up the application (see Resources). Click on Developer App in the Helpful Links to go to your user profile and add this developer application. If you are not already logged in, a login screen will prompt you for login. Otherwise, the application asks for authorization and will add the application to your profile (see Figure 14).
Figure 14. Get Started
The developer's home page contains the news, updates, and articles about the Facebook Platform API.
Enter a name for your application in the Application Name field (see Figure 15). If you have already created the icon and logo for your application, you can enter this information at this time in the same screen. Accept the developer terms of service, then click Save Changes.
Figure 15. Naming the application
In the next screen shown in Figure 16, important information is displayed. It is important to note the Application ID, API Key, and Secret Key for future application development.
Figure 16. Application ID, API Key, and Secret Key are displayed
Once you enter the required information and save the new application, an overview of the RestaurantSearch application information is displayed (see Figure 17).
Figure 17. Overview of application
By now, you have created and registered an application named SimpleRestaurantSearch with Facebook. The next step creates a simple servlet and adds functionality to authenticate the Facebook API key. In the Project Explorer, go to the SimpleRestaurantSearch project, then create a servlet in the src folder. Name the servlet RestaurantSearch and enter the package name as com.devworks.facebook. Click Next to enter the servlet initialization parameters (see Figure 18).
Figure 18. Creating a simple servlet
In the next screen shown in Figure 19, enter the Initialization Parameters API_KEY and the value as the API key in our initial steps of Facebook application creation.
Figure 19. Entering the Initialization Parameters API_KEY
On the next screen, enter the Initialization Parameters SECRET_KEY and the value as the secret key in our initial steps of Facebook application creation.
This is the time to use the API_KEY and SECRET_KEY to authenticate the Facebook application, and if the login is successful, print a simple Hello World message.
Listing 1 is the critical segment of the doGet method of our RestaurantSearch servlet.
Listing 1. doGet method
01 protected void doGet(HttpServletRequest request,
02 HttpServletResponse response) throws ServletException,IOException {
03
04 String apiKey = getServletConfig().getInitParameter("API_KEY");
05 String secretKey = getServletConfig().getInitParameter("SECRET_KEY");
06 HttpSession session = request.getSession();
07 String sessionKey = (String) session
08 .getAttribute("restSearchAppSession");
09 String authToken = request.getParameter("auth_token");
10
11 FacebookJsonRestClient client = null;
12
13 if (sessionKey != null) {
14 client = new FacebookJsonRestClient(apiKey,
15 secretKey,
16 sessionKey);
17
18 } else if (authToken != null) {
19 client = new FacebookJsonRestClient(apiKey, secretKey);
20 client.setIsDesktop(false);
21 try {
22 sessionKey = client.auth_getSession(authToken);
23 session.setAttribute("restSearchAppSession", sessionKey);
24 } catch (Exception e) {
25 e.printStackTrace();
26 }
27 } else {
28 response.sendRedirect("http://www.facebook.com/login.php?api_key="+apiKey);
29 return;
30 }
31 response.getWriter().println("HelloWorld");
32 }
Lines 4 and 5 get the initial parameters such as API_KEY and SECRET_KEY from servlet configuration.
Line 7 gets the session key from the session if it's already present, else it would be null.
Line 9 gets the authentication token from the request parameter. It could be null if the session is not authenticated.
If a sessionKey exists, Line 14 creates a FacebookJsonRestClient and needs the apiKey, secretKey, and sessionKey as constructor arguments (see Figure 20).
Figure 20. Creating a FacebookJsonRestClient
If a sessionKey does not exist, create a FacebookJsonRestClient with only the apiKey and secretKey. On line 20, make sure to set the correct client mode.
It's important that your application is set to the correct mode. If it is set to "desktop mode is false," the Facebook server will understand when you try to pass a session secret.
In lines 22 and 23, create the sessionKey with the help of authentication token and set it to the session attribute restSearchAppSession.
If there is no sessionKey and no authentication token that implies that the user needs to log in to the Facebook and get a new session and auth key. Thus, the Line 28 redirects to Facebook login.
Finally, print Hello World on the output writer, as shown in line 31.
Once the RestaurantSearch application is complete, you can start the Tomcat server. Remember that in the initial steps of cresting the SimpleRestaurantSearch application, you have already associated this project with the Tomcat server EclipseBook-Host. From the server view, start Tomcat. This will start the Tomcat server in Eclipse and will deploy the application (see Figure 21).
Figure 21. Starting the Tomcat server in Eclipse and deploying the application
Once the Tomcat server is started, browse to http://localhost:8080/SimpleRestaurantSearch/RestaurantSearch. This will take you to a Facebook developer page that informs you that the site is under construction and suggests you that the application Callback URL is not set. Click on the applications settings editor (see Figure 22).
Figure 22. The applications settings editor
In the application settings editor, go to the Canvas tab and enter the Canvas page URL (http://apps.facebook.com/devrestaurantsearch), Canvas Callback URL (http://localhost:8080/SimpleRestaurantSearch/RestaurantSearch), and Bookmark URL (http://apps.facebook.com/devrestaurantsearch). Save the settings (see Figure 23).
Figure 23. Application settings editor
Once the new settings are saved, the Application Overview page is displayed (see Figure 24).
Figure 24. Application Overview
The real power of Eclipse is the integrated Tomcat and hot deployment capability. You can simply restart the server now and see if the saved application properties are in effect (see Figure 25).
Figure 25. Restarting the server
Now when the server is restarted within Eclipse Galileo, the RestaurantSearch servlet will redirect you to the app login page (http://www.facebook.com/login.php?api_key=). Once you enter your Facebook's e-mail ID and password, the servlet will write the response out.
From the Facebook application screen, it can be understood that the API_KEY is used to log in to the appropriate application. In this case, it is SimpleRestaurantSearch (see Figure 26).
Figure 26. Application login
Finally, the Facebook application is authenticated, and once the sessionKey and authKey are generated, Hello World is displayed on the screen (see Figure 27).
Figure 27. Hello World is displayed
Log off from Facebook and try to access the application on http://www.facebook.com/apps/application.php?id=144078916555. Facebook displays the application information, and you can access it by logging in (see Figure 28).
Figure 28. Login page
In the next steps, you will use the Google Search API and integrate it into a simple JSP.
Back to top
Integrate Google Search API into the Facebook application
The Google Ajax Search API lets you put Google Search in your Web pages with JavaScript. You can embed a simple dynamic search box and display search results in your own Web pages or use the results in innovative, programmatic ways. You do not need a key to use this API. Using a key in your application/site is completely optional. However, it is useful to have one.
Go to http://code.google.com/apis/ajaxsearch/signup.html and agree to the terms and conditions. Click on the Generate API Key (see Figure 29).
Figure 29. Generating the API key
Google generates API key and shows the URL for which this API is good. This Web page also provides examples to get started (see Figure 30).
Figure 30. Google-generated API key
Copy the provided example code from the above Google Search to RestaurantSearch.jsp in the WebContent folder. Save the JSP and make sure to change the code in SimpleRestaurantSearch from writing the response Hello World to dispatch the request to the RestaurantSearch.jsp.
Change the code from response.getWriter().println("Hello World"); to request.getRequestDispatcher("RestaurantSearch.jsp").forward(request,response);.
The moment the JSP is saved, the entire project gets redeployed to the Tomcat server automatically. In the previous steps, you set the Canvas URL (http://apps.facebook.com/devrestaurantsearch) and also the Canvas Callback URL (http://localhost:8080/SimpleRestaurantSearch/RestaurantSearch) (see Figure 31).
Figure 31. Settings for the Canvas URL and the Canvas Callback URL
If you access the Canvas URL, and once you have successfully logged in, RestaurantSearch.jsp starts the RestaurantSearch application (see Figure 32).
Figure 32. Starting up the RestaurantSearch application
The application bookmark is in the bottom left corner of the application toolbar. You can enter a search string for a restaurant search (see Figure 33).
Figure 33. Application bookmark in the application toolbar
Change the default location in the Google Maps and set the default maps view to NORMAL View in RestaurantSearch.jsp (see Listing 2).
Listing 2. Changing the default location in Google Maps
// change the default location in the Google Maps
map.setCenter(new google.maps.LatLng(37.773,-122.417),13);
// set the Map to Normal view
map.setMapType(G_NORMAL_MAP);
map.removeMapType(G_HYBRID_MAP);
map.addMapType(G_NORMAL_MAP);
Save the JSP to hot-deploy and retest it to make sure that the location and map type are changed (see Figure 34). We have now chosen San Francisco as the default search location. Once this application is running in Facebook, when a user searches for a type of restaurant, he can add a ZIP code for the location, and the application will return mapped restaurant results in that location.
Figure 34. Redeploying and retesting the application
Now you can test further by navigating to your Facebook profile and searching for the SimpleRestaurantSearch application in the search box in the top right corner (see Figure 35).
Figure 35. Searching for the SimpleRestaurantSearch application from your Facebook profile
Application Search will take you to the SimpleRestaurantSearch application (see Figure 36).
Figure 36. Application Search takes you to the SimpleRestaurantSearch application
Back to top
Integrating the Facebook Connect API
Facebook Connect allows you to leverage Facebook for your own off-Facebook applications. You could use the Facebook connect API on your site and let your viewers share content on their own profiles.
You will need to create a cross-domain communication channel file called xd_receiver.htm and place it in a directory relative to the callback URL. You should create the xd_receiver.htm file in the directory from where you'll be serving your Connect Web pages (WebContent folder in our example). See Figure 37.
Figure 37. Creating and saving a cross-domain communication channel
An example of a cross-domain channel file is shown in Listing 3. You can copy the following content and create the xd_receiver.htm in the WebContent folder. Without a cross-domain channel file, Facebook will not be able to communicate correctly with our application server (see Listing 3).
Listing 3. A cross-domain channel file
The quickest way to start using Facebook Connect on your server is to use the JavaScript API library. The two essential properties of connecting to the library are setting the correct document type and loading the JavaScript library at the end of your Web page, near the
Before you begin developing your Facebook SimpleRestaurantSearch application, you need to download and install the Galileo package of Eclipse (see Resources). In this section, you'll learn how to set it up.
Downloading Galileo
The Galileo package represents the next incremental release for Eclipse, and as such, means a new installation of the Eclipse platform. As with all Eclipse releases, there are a number of packages to choose from, depending upon your development needs.
Download the Eclipse IDE for Java™ EE Developers version, as it has everything you need to develop and deploy a Facebook application. Choose the version for your operating system, select an appropriate mirror, and download it (see Resources). The file is quite large — close to 190 MB depending on your platform — so be patient.
The Eclipse Web site provides a comparison chart, shown in Figure 1.
Figure 1. Package comparison chart
When the download is complete, unzip the package where you want Eclipse to be installed, then double-click the Eclipse icon to run it. Select a workspace, and Eclipse will take you to the welcome page. From here, choose the Workbench icon (the arrow on the far right of the welcome screen shown in Figure 2).
Figure 2. Eclipse Welcome screen
Setting up Tomcat in Eclipse
Eclipse Galileo allows you to integrate variety of servers so that any Web applications can be developed, debugged, and deployed. For the current Facebook SimpleRestaurantSearch application, you would use Tomcat as the application server (see Resources). Download Tomcat to a local folder and extract it.
Switch to Eclipse and open the server view (see Figure 3).
Figure 3. Server view in Eclipse
Right-click on the server view and select New > Server menu option (see Figure 4).
Figure 4. New server menu option
Define a new server by selecting the appropriate options. Select the Tomcat V6 Server option under Apache category. You can name the server as anything meaningful for the application like EclipseBook-Host, then click Next (see Figure 5).
Figure 5. Defining a new server
In the next wizard window, enter the Tomcat installation directory, select the required JRE, then click Finish (see Figure 6).
Figure 6. Setting the installation directory
Once Tomcat is properly configured, the server appears in the server view. By default, the server port is set to 8080 (see Figure 7).
Figure 7. Server appears in the server view
Next, we'll set up the Dynamic Web Project so you can work with your application's Web interface from within Eclipse.
Setting up the Dynamic Web Project
Click on the Project Explorer, and right-click and select the Dynamic Web Project (see Figure 8).
Figure 8. Setting up the Dynamic Web Project
Give the project a name and set the target runtime to be the Tomcat Server name. Remember that you name the Tomcat Server as EclipseBook-Host. Click Finish to create the Web project configured to use the Tomcat server and default Web configuration (see Figure 9).
Figure 9. Creating the Web project
Back to top
Downloading and setting up the Facebook Java API
As of May 2008, Facebook has discontinued any support of its official Java client, directing users interested developing Facebook applications in Java technology to use one of the various third-party clients out there. One of the popular Facebook Java APIs is available on Google (see Resources). As such, the purpose of this project is now to maintain, support, and extend the abandoned code base to provide a high-quality, up-to-date version of the Facebook API client for Java developers (see Figure 10).
Figure 10. Facebook Java API
Download the latest Java Facebook API (V3.0.0) into the local folder and extract the files (see Figure 11).
Figure 11. Downloading the latest Facebook Java API
The Facebook Java API contains all the libraries related to the Facebook Application API and other dependent JARs (see Figure 12). See Download for the source code of our sample application. Note that the JAR files aren't included in that ZIP file, since you download them here with the Facebook Java API.
Figure 12. Libraries related to the Facebook Application API and other dependent JARs
Copy all the Facebook Java Client JARs to the lib folder of the SimpleRestaurantSearch application. This will now enable the project to use the Facebook APIs (see Figure 13).
Figure 13. Copy all the Facebook Java Client JARs to lib folder
Back to top
Creating a Facebook application
Almost everyone has a presence on Facebook, including Web developers, business managers, and social geeks. Creating applications on the Facebook platform that leverage the Facebook Application API opens a window of visibility for users of all stripes, whether they wish to advertise a product or service or simply share information with friends.
To create a Facebook application, you first need to obtain a Facebook Platform API key. Follow these steps to create an application with the Facebook Developer application.
Go to the Get Started site to get an overview of the steps for setting up the application (see Resources). Click on Developer App in the Helpful Links to go to your user profile and add this developer application. If you are not already logged in, a login screen will prompt you for login. Otherwise, the application asks for authorization and will add the application to your profile (see Figure 14).
Figure 14. Get Started
The developer's home page contains the news, updates, and articles about the Facebook Platform API.
Enter a name for your application in the Application Name field (see Figure 15). If you have already created the icon and logo for your application, you can enter this information at this time in the same screen. Accept the developer terms of service, then click Save Changes.
Figure 15. Naming the application
In the next screen shown in Figure 16, important information is displayed. It is important to note the Application ID, API Key, and Secret Key for future application development.
Figure 16. Application ID, API Key, and Secret Key are displayed
Once you enter the required information and save the new application, an overview of the RestaurantSearch application information is displayed (see Figure 17).
Figure 17. Overview of application
By now, you have created and registered an application named SimpleRestaurantSearch with Facebook. The next step creates a simple servlet and adds functionality to authenticate the Facebook API key. In the Project Explorer, go to the SimpleRestaurantSearch project, then create a servlet in the src folder. Name the servlet RestaurantSearch and enter the package name as com.devworks.facebook. Click Next to enter the servlet initialization parameters (see Figure 18).
Figure 18. Creating a simple servlet
In the next screen shown in Figure 19, enter the Initialization Parameters API_KEY and the value as the API key in our initial steps of Facebook application creation.
Figure 19. Entering the Initialization Parameters API_KEY
On the next screen, enter the Initialization Parameters SECRET_KEY and the value as the secret key in our initial steps of Facebook application creation.
This is the time to use the API_KEY and SECRET_KEY to authenticate the Facebook application, and if the login is successful, print a simple Hello World message.
Listing 1 is the critical segment of the doGet method of our RestaurantSearch servlet.
Listing 1. doGet method
01 protected void doGet(HttpServletRequest request,
02 HttpServletResponse response) throws ServletException,IOException {
03
04 String apiKey = getServletConfig().getInitParameter("API_KEY");
05 String secretKey = getServletConfig().getInitParameter("SECRET_KEY");
06 HttpSession session = request.getSession();
07 String sessionKey = (String) session
08 .getAttribute("restSearchAppSession");
09 String authToken = request.getParameter("auth_token");
10
11 FacebookJsonRestClient client = null;
12
13 if (sessionKey != null) {
14 client = new FacebookJsonRestClient(apiKey,
15 secretKey,
16 sessionKey);
17
18 } else if (authToken != null) {
19 client = new FacebookJsonRestClient(apiKey, secretKey);
20 client.setIsDesktop(false);
21 try {
22 sessionKey = client.auth_getSession(authToken);
23 session.setAttribute("restSearchAppSession", sessionKey);
24 } catch (Exception e) {
25 e.printStackTrace();
26 }
27 } else {
28 response.sendRedirect("http://www.facebook.com/login.php?api_key="+apiKey);
29 return;
30 }
31 response.getWriter().println("HelloWorld");
32 }
Lines 4 and 5 get the initial parameters such as API_KEY and SECRET_KEY from servlet configuration.
Line 7 gets the session key from the session if it's already present, else it would be null.
Line 9 gets the authentication token from the request parameter. It could be null if the session is not authenticated.
If a sessionKey exists, Line 14 creates a FacebookJsonRestClient and needs the apiKey, secretKey, and sessionKey as constructor arguments (see Figure 20).
Figure 20. Creating a FacebookJsonRestClient
If a sessionKey does not exist, create a FacebookJsonRestClient with only the apiKey and secretKey. On line 20, make sure to set the correct client mode.
It's important that your application is set to the correct mode. If it is set to "desktop mode is false," the Facebook server will understand when you try to pass a session secret.
In lines 22 and 23, create the sessionKey with the help of authentication token and set it to the session attribute restSearchAppSession.
If there is no sessionKey and no authentication token that implies that the user needs to log in to the Facebook and get a new session and auth key. Thus, the Line 28 redirects to Facebook login.
Finally, print Hello World on the output writer, as shown in line 31.
Once the RestaurantSearch application is complete, you can start the Tomcat server. Remember that in the initial steps of cresting the SimpleRestaurantSearch application, you have already associated this project with the Tomcat server EclipseBook-Host. From the server view, start Tomcat. This will start the Tomcat server in Eclipse and will deploy the application (see Figure 21).
Figure 21. Starting the Tomcat server in Eclipse and deploying the application
Once the Tomcat server is started, browse to http://localhost:8080/SimpleRestaurantSearch/RestaurantSearch. This will take you to a Facebook developer page that informs you that the site is under construction and suggests you that the application Callback URL is not set. Click on the applications settings editor (see Figure 22).
Figure 22. The applications settings editor
In the application settings editor, go to the Canvas tab and enter the Canvas page URL (http://apps.facebook.com/devrestaurantsearch), Canvas Callback URL (http://localhost:8080/SimpleRestaurantSearch/RestaurantSearch), and Bookmark URL (http://apps.facebook.com/devrestaurantsearch). Save the settings (see Figure 23).
Figure 23. Application settings editor
Once the new settings are saved, the Application Overview page is displayed (see Figure 24).
Figure 24. Application Overview
The real power of Eclipse is the integrated Tomcat and hot deployment capability. You can simply restart the server now and see if the saved application properties are in effect (see Figure 25).
Figure 25. Restarting the server
Now when the server is restarted within Eclipse Galileo, the RestaurantSearch servlet will redirect you to the app login page (http://www.facebook.com/login.php?api_key=
From the Facebook application screen, it can be understood that the API_KEY is used to log in to the appropriate application. In this case, it is SimpleRestaurantSearch (see Figure 26).
Figure 26. Application login
Finally, the Facebook application is authenticated, and once the sessionKey and authKey are generated, Hello World is displayed on the screen (see Figure 27).
Figure 27. Hello World is displayed
Log off from Facebook and try to access the application on http://www.facebook.com/apps/application.php?id=144078916555. Facebook displays the application information, and you can access it by logging in (see Figure 28).
Figure 28. Login page
In the next steps, you will use the Google Search API and integrate it into a simple JSP.
Back to top
Integrate Google Search API into the Facebook application
The Google Ajax Search API lets you put Google Search in your Web pages with JavaScript. You can embed a simple dynamic search box and display search results in your own Web pages or use the results in innovative, programmatic ways. You do not need a key to use this API. Using a key in your application/site is completely optional. However, it is useful to have one.
Go to http://code.google.com/apis/ajaxsearch/signup.html and agree to the terms and conditions. Click on the Generate API Key (see Figure 29).
Figure 29. Generating the API key
Google generates API key and shows the URL for which this API is good. This Web page also provides examples to get started (see Figure 30).
Figure 30. Google-generated API key
Copy the provided example code from the above Google Search to RestaurantSearch.jsp in the WebContent folder. Save the JSP and make sure to change the code in SimpleRestaurantSearch from writing the response Hello World to dispatch the request to the RestaurantSearch.jsp.
Change the code from response.getWriter().println("Hello World"); to request.getRequestDispatcher("RestaurantSearch.jsp").forward(request,response);.
The moment the JSP is saved, the entire project gets redeployed to the Tomcat server automatically. In the previous steps, you set the Canvas URL (http://apps.facebook.com/devrestaurantsearch) and also the Canvas Callback URL (http://localhost:8080/SimpleRestaurantSearch/RestaurantSearch) (see Figure 31).
Figure 31. Settings for the Canvas URL and the Canvas Callback URL
If you access the Canvas URL, and once you have successfully logged in, RestaurantSearch.jsp starts the RestaurantSearch application (see Figure 32).
Figure 32. Starting up the RestaurantSearch application
The application bookmark is in the bottom left corner of the application toolbar. You can enter a search string for a restaurant search (see Figure 33).
Figure 33. Application bookmark in the application toolbar
Change the default location in the Google Maps and set the default maps view to NORMAL View in RestaurantSearch.jsp (see Listing 2).
Listing 2. Changing the default location in Google Maps
// change the default location in the Google Maps
map.setCenter(new google.maps.LatLng(37.773,-122.417),13);
// set the Map to Normal view
map.setMapType(G_NORMAL_MAP);
map.removeMapType(G_HYBRID_MAP);
map.addMapType(G_NORMAL_MAP);
Save the JSP to hot-deploy and retest it to make sure that the location and map type are changed (see Figure 34). We have now chosen San Francisco as the default search location. Once this application is running in Facebook, when a user searches for a type of restaurant, he can add a ZIP code for the location, and the application will return mapped restaurant results in that location.
Figure 34. Redeploying and retesting the application
Now you can test further by navigating to your Facebook profile and searching for the SimpleRestaurantSearch application in the search box in the top right corner (see Figure 35).
Figure 35. Searching for the SimpleRestaurantSearch application from your Facebook profile
Application Search will take you to the SimpleRestaurantSearch application (see Figure 36).
Figure 36. Application Search takes you to the SimpleRestaurantSearch application
Back to top
Integrating the Facebook Connect API
Facebook Connect allows you to leverage Facebook for your own off-Facebook applications. You could use the Facebook connect API on your site and let your viewers share content on their own profiles.
You will need to create a cross-domain communication channel file called xd_receiver.htm and place it in a directory relative to the callback URL. You should create the xd_receiver.htm file in the directory from where you'll be serving your Connect Web pages (WebContent folder in our example). See Figure 37.
Figure 37. Creating and saving a cross-domain communication channel
An example of a cross-domain channel file is shown in Listing 3. You can copy the following content and create the xd_receiver.htm in the WebContent folder. Without a cross-domain channel file, Facebook will not be able to communicate correctly with our application server (see Listing 3).
Listing 3. A cross-domain channel file
The quickest way to start using Facebook Connect on your server is to use the JavaScript API library. The two essential properties of connecting to the library are setting the correct document type and loading the JavaScript library at the end of your Web page, near the
