Apex REST Content Challenge


Apex REST Content Challenge

With Apex REST, you can implement custom Web services in Apex and expose them as RESTful services for external clients to call.

> Back to Developer Content Challenge Home Page

Challenge Requirements

Here's what we're looking for in this challenge.

General

In this challenge, we want you to write a detailed "Getting Started" article on the use of Apex REST.

  • Start the reader with some basics and context for REST and why it's important these days.
  • Build your article around a demo app that uses Apex classes exposed as RESTful services.
  • Show how authentication works with Apex REST, specifically using OAuth 2.0.
  • Thoroughly explain your code, what you are doing, and why you are doing it. Don't assume that the reader can read your mind ;-)

Please note that there have been some updates made to Apex REST in Spring '12, so make sure that you are aware of these changes (see links below).

Article

Dates

This contest is now closed.

  • Start Date: February 07, 2012
  • End Date: 11:59PM Pacific Time, February 21, 2012. No exceptions.
  • Award Date: No later than 12AM Pacific Time, February 29, 2012

Prizes

The winning entry will receive a US$1000 gift card and the associated content will be published on Developer Force.

Submission Details

See Developer Contest Rules for eligibility requirements and other details.

1. Send an email with the following.

  • Subject: Apex REST Content Challenge Submission
  • To: editors@developerforce.com
  • Body: Your contact information, including full name, address, and preferred email address.

2. Attach a zip archive with any supporting source code, documentation, and the article.

3. Look for a receipt of submission from us within 24 hours.

You may receive feedback on your initial submission to help you improve your work before making your submission final. Your final submission will be judged by a panel of peers based upon this scorecard.

Helpful Info

Challenge Scorecard

Here is the weighted criteria that judges will use to score submissions for this challenge.

Requirements (20%)

  • The solution addresses all the requirements as specified in the project posting request. The reviewer must be able to find all of the requirements implemented in the returned solution. (1 - 4)
  • Is the code appropriately scoped? Does is it not over design for the current task? (1 - 4)

Documentation/Readability (30%)

  • An article with the submission. The article is well-written and clearly articulates the steps necessary to deploy the system. (1 - 4)
  • The code is clear, well-written and documented clearly. (1 - 4)
  • All hard-coded values are called out directly in the deploy document. Clear instructions for replacing all hard coded values are present. (1 - 4)
  • Is the code well documented? Are there code comments where necessary? (1 - 4)

Code Quality (30%)

  • Is the code appropriately batched? Code should not be operated on individual items if possible. (1 - 4)
  • Is the code thoroughly covered with clear, functional unit tests? (1 - 4)
  • Does the code successfully deploy into a clean Developer Edition org? (1 - 4)

Innovation (20%)

  • Does the application match all of the expected functionality and exceed expectations. (1 - 4)