Home > Articles > Programming > Java

📄 Contents

  1. Annotations
  2. Coding a REST CRUD Service
Like this article? We recommend Coding a REST CRUD Service

Coding a REST CRUD Service

As with my previous introduction article to RESTful services using JAX-RS, the steps for setting up the project are similar and shown below for convenience, along with a few changes.

Step 1: Download a Reference Implementation to JAX-RS

In order to get started, you need to download a reference implementation of JAX-RS provided by the GlassFish project. Jersey provides a servlet that analyzes the incoming HTTP request and selects the correct class and method to respond to this request. This selection is based on annotation in the class and methods.

You can download Jersey zip file (core dependencies) from the Jersey website.

Step 2: Create Your Java Project

Using Eclipse, NetBeans, Maven, or whatever you like, create the project's directory structure (i.e., with Eclipse, use Dynamic Web Project). I'm calling the project jaxrscrud.

Next, copy all the Jersey core-dependency jars into the WEB-INF/lib folder of the project.

Step 3: Register the Jersey Reference Implementation Servlet with the Project

In order to get Jersey intercepting the requests, you need to modify the Web.xml file like the following:

<?xml version="1.0" encoding="UTF-8"?> 
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns="http://java.sun.com/xml/ns/javaee" 
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
 http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
id="WebApp_ID" version="2.5"> 
<display-name>jaxrscrud</display-name> <servlet> 
<servlet-name>Jersey REST Service</servlet-name> 
<servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class> 
<init-param> <param-name>com.sun.jersey.config.property.packages</param-name> 
<param-value>crudOperations</param-value> </init-param> 
<load-on-startup>1</load-on-startup> </servlet> 
<servlet-mapping> <servlet-name>Jersey REST Service</servlet-name> 
<url-pattern>/rest/*</url-pattern> </servlet-mapping> </web-app> 

The parameter com.sunjersey.config.property.packages should have the package where the web service classes can be found. In this example, the crudOperations package will contain these classes.

Step 4: Set Up a Database and JPA

For purposes of this section, I'm going to reuse the second page from an earlier article I wrote for doing these tasks. Perform the steps starting at the section titled "Configuring Apache Derby to Work with Eclipse" near the top of the page. Stop performing these steps when you reach the section labeled "Adding the User Entity Class, Login, and Welcome Pages." The last step should be adding a persistence.xml file to your project. The only thing to replace in the persistence.xml file code is the package where the Users class will reside. logon.User should be changed to crudOperations.User (see step 5). Also, add a few records to your new database table, so the service will have some data to work with.

Step 5: Create a Package Called crudOperations

While crudOperations is a bit vague, we would normally be more specific if exposing a particular application's Entity class (in this example, a class called Users). For example, we would probably just keep the class name the same, or if we're going to bundle several Entity classes for CRUD operations, then the vague package name would be more applicable.

Step 6: Create the User Entity Class that Will Map the User Object to the Users Database Table Created in Step 3

Because we are using the User Entity class from a previous article, copy the code for that class into the crudOperations package. The code is the first code section under the section labeled "Adding the User Entity Class, Login, and Welcome Pages."

Step 7: Create a Class that Registers Itself with a GET HTTP Request to Perform a Read Operation Using the User Entity Class

To expose this class as a RESTful web service, a few annotations were added to the code:

package crudOperations;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import javax.ws.rs.core.MediaType;
import java.util.List; 
import javax.persistence.EntityManager; 
import javax.persistence.EntityManagerFactory; 
import javax.persistence.Persistence; 
import javax.persistence.Query;
@Path("/users")
public class Users {
    private static final String PERSISTENCE_UNIT_NAME = "User";
    private static EntityManagerFactory factory;
    private static String userName = null;
    
    // This method is called if TEXT_PLAIN is request
    @GET
    @Produces(MediaType.TEXT_PLAIN)
    public String userList() {
        factory = Persistence.createEntityManagerFactory
            (PERSISTENCE_UNIT_NAME);
        EntityManager em = factory.createEntityManager(); 
        Query q = em.createQuery("SELECT u FROM User u"); 
        List<User> userList = q.getResultList();
         for (User user : userList) { 
            userName = user.Name; 
        } 
         return userName;
    }
}

The class is small right now, but if a request is made to the path users, the service will return the last user name in the table. By doing this, we know our service is interfacing with the database and returning data appropriately.

The @GET annotation tells Jersey to map this method of the class to the HTTP GET method. The @Produces annotation tells the servlet to respond with the correct content type based on the request.

Step 8: Add the JPA Facet to Your Project

Another step that needs to be performed is adding the JPA Facet to your project. Right-click your project (if in Eclipse) and choose the JPA Facet. Once you click OK, you'll see a new section added to your project called JPA content. Copy the code from your WEB-CONTENT/META-INF/persistence.xml file into the persistence.xml file of this section.

Step 9: Test the Service

To test the service, browse to the URL hosting the "RESTlet": http://localhost:8080/jaxrscrud/rest/users.

Because the content type of our Request Header was for plain text, the service returns the last user name in the users table to the screen. While the scope of this article started with an existing class and doing the application set up, you only need to do the last few steps for an existing Java application.

Conclusion

This simple example should be enough to get you started with exposing existing or new Entity classes as RESTful services. In a later article, I'd like to expand on this example to include a web-based client using AJAX and JSON to use the service. The expanded example will show how to send and consume data from the service using basic HTML web forms.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020