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

Java Source Code to Change Local IP Address

Hi guys..

Try This code to change your Local IP address.


import java.io.IOException;
import java.lang.Runtime;
public class Chang_Ip {



public static void main(String args[]) throws IOException
{

String str1="192.168.0.201";
String str2="255.255.255.0";
String[] command1 = { "netsh", "interface", "ip", "set", "address",
"name=", "Local Area Connection" ,"source=static", "addr=",str1,
"mask=", str2};
Process pp = java.lang.Runtime.getRuntime().exec(command1);

}


}

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 LocationKeep-AliveContent-LengthContent-TypeDateServerUser-AgentHostNhttp transport – support headersServerUser-AgentDate
You can specify header fields which should be preserved in a comma-separated list, as shown below. http.headers.preserve = Location, Date, Server Note that properties(http.user.agent.preserve, http.server.preserve), which were used …

How Schedule failover message processor helps for the guaranteed delivery ?

Before we talk about the failover message forwarding processor, it’s better to understand the big picture of the concepts and use cases. The Scheduled Failover Message Forwarding Processor is part of the bigger picture of themessage store and message processor.

Message Store Message Processor. WSO2 ESB’s Message-stores and Message-processorsare used to store incoming messages and then deliver them to a particular backend with added Quality of Services (QoS), such as throttling and guaranteed delivery. The basic advantage of the MSMP is that it allows you to send messages reliably to a backend service. These messages can be stored in a different reliable storage such as JMS, JDBC message stores. The MSMP powered by three basic components:



1. Store Mediator.
The Store mediator is the synapse mediator and can be used to store messages in the message store.

2. Message Store.
A message store is storage in the ESB for messages. The WSO2 ESB comes with four types of message store implementations …