Skip to main content

Embedded jetty for JAXRS

In this tutorial, we show you how to develop a simple RESTfull web service application with embedded jetty server using cuubez framwork.
Technologies and Tools used in this article:
  1. cuubez 1.1.1
  2. JDK 1.7
  3. Maven 3.0.3
  4. Intellij IDEA 13.1.1
Note: If you want to know what and how REST works, just search on Google, ton of available resources.

1. Directory Structure

This is the final web project structure of this tutorial.

2. Standard Java Project

Create a standard Maven java project structure
 mvn archetype:generate -DgroupId=com.cuubez -DartifactId=cuubez-jetty -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false  

Note: To support IntelliJ IDEA, use Maven command :
mvn idea:idea

3. Project Dependencies

Following maven dependencies should add to the pom.xml file.
File : pom.xml


 <dependency>  
  <groupId>com.cuubez</groupId>  
  <artifactId>cuubez-core</artifactId>  
  <version>1.1.1</version>  
 </dependency>  
 <dependency>  
  <groupId>org.eclipse.jetty</groupId>  
  <artifactId>jetty-servlet</artifactId>  
  <version>8.0.4.v20111024</version>  
 </dependency>  

4. REST Service

 @Path("/users/{userId}")  
 @Produces(MediaType.APPLICATION_JSON)  
 public class UserResource {  
   private static Log log = LogFactory.getLog(UserResource.class);  
   @GET  
   @Produces(MediaType.APPLICATION_JSON)  
   public Response userGet(@PathParam(value = "userId") String id, @QueryParam(value = "name") String name, @QueryParam(value = "age") int age) {  
     User user = new User(id, age, name);  
     return Response.ok().entity(user).build();  
   }  
   @Consumes(MediaType.APPLICATION_JSON)  
   @POST  
   public void userPost(User user) {  
     log.info("POST = [" + user + "]");  
   }  
   @PUT  
   @Consumes({MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML})  
   public void userPut(User user) {  
     log.info("PUT = [" + user + "]");  
   }  
 }  

5. Embedded Jetty Implementation

 public class JettyServer {  
   public static void main(String args[]) {  
     Server server = new Server(8080);  
     ServletContextHandler handler = new ServletContextHandler(ServletContextHandler.SESSIONS);       
     server.setHandler(handler);  
     handler.setContextPath("/");  
     handler.setResourceBase(".");  
     handler.addEventListener(new BootstrapContextListener()); //cuubez bootstrap context listner  
     handler.addServlet(HttpServletDispatcher.class, "/rest/*"); //servlet filter  
     try {  
       server.start();  
       server.join();  
     } catch (Exception e) {  
       e.printStackTrace();  
     }  
   }  
 }  

6. Demo

In this example, web request from projectURL/rest/users/id-1003 will match to UserResource, via @Path("/users/{userId}"). {userId} will match to parameter annotated with @PathParam and age and name will match to parameters annotated with @QueryParam


Download this example - cuubez-jetty.zip

Comments

Popular posts from this blog

How to enable proxy service security in ESB 4.9.0?

Security is  one of the major concern when we developing API base integrations or application developments. WSO2 supports WS Security , WS-Policy and WS-Security Policy specifications. These specifications define a behavior model for web services. Proxy service security requirements are different from each others. WSO2 ESB providing pre-define commonly used twenty security scenarios to choose based on the security requirements. This functionality is provided by the security management feature which is bundled by default in service management feature in ESB. This configuration can be done via the web console until ESB 4.8.1 release, but this has been removed from the ESB 4.9.0. Even though this feature isn't provided by the ESB web console itself same functionality can be achieved by the new WSO2 Dev Studio . WSO2 always motivate to use dev studio to prepare required artifacts to the ESB rather than the web console. Better way to explain this scenario is by example. Following...

How to preserving HTTP headers in WSO2 ESB 4.9.0 ?

Preserving HTTP headers are important when executing backend services via applications/middleware. This is because most of the time certain important headers are removed or modified by the applications/middleware which run the communication. The previous version of our WSO2 ESB, version 4.8.1, only supported “ server ” and “ user agent ” header fields to preserve with, but with the new ESB 4.9.0, we’ve introduced a new new property ( http.headers.preserve ) for the passthru ( repository/conf/ passthru-http.properties ) and Nhttp( repository/conf/ nhttp.properties ) transporters to preserve more HTTP headers. Passthru transporter – support header fields               Location Keep-Alive Content-Length Content-Type Date Server User-Agent Host Nhttp transport – support headers Server User-Agent Date You can specify header fields which should be preserved in a comma-separated list, as shown below. http.headers.p...

How to write a Synapse Handler for the WSO2 ESB ?

Synapse handler is new feature which come with the ESB 4.9.0. It provide abstract handler implementation to the users. User can create their own concrete handlers which is executing in the synapse layer. Main intention of this blog post is to explain how to write synapse handler and explain basic theoretical background. 1. What is the handler? Handlers are basically talking with the chain of responsibility pattern. Chain of responsibility allows a number of classes to attempt to handle a request independently of any other object along the chain. Once the request is handled, it completes it's journey through the chain. The Handler defines the interface which required to handle the request and concreteHandlers handle request in a specific manner that they are responsible for. 2. What is Synapse handler? Synapse handler is providing abstract handle implementation which executes in the following four scenarios. 1. Request in flow This is exe...