Skip to main content

Java Vs Groovy - Enum Demo

 Java 5 introduced enum that solve the problem with enumeration. Groovy also support that feature, as shown here.
 Enum example using Java.
enum ShirtSize {
 SMALL,MEDIUM,LARGE,EXTRALARGE
}

class ShirtImplementation {
 public void orderShirt(ShirtSize size) {
  switch(size) {
   case SMALL :
    System.out.println("The size of the shirt is small");
    break;
   case MEDIUM :
    System.out.println("The size of the shirt is medium");
    break;
   case LARGE :
    System.out.println("The size of the shirt is large");
    break;
   case EXTRALARGE :
    System.out.println("The size of the shirt is extra large");
    break;
   default : 
    System.out.println("The shirt size is not available");
    break;
    
  }
 }
}

public class EnumExample {
 public static void main(String args[]) {
  ShirtImplementation shirtImplementation = new ShirtImplementation();
  shirtImplementation.orderShirt(ShirtSize.SMALL);
  shirtImplementation.orderShirt(ShirtSize.MEDIUM);
  shirtImplementation.orderShirt(ShirtSize.LARGE);
  shirtImplementation.orderShirt(ShirtSize.EXTRALARGE);
 }
}
The output from the above code is as follows
The size of the shirt is small
The size of the shirt is medium
The size of the shirt is large
The size of the shirt is extra large
Groovier way for implementing above example
enum ShirtSize {
 SMALL,MEDIUM,LARGE,EXTRALARGE
}

def orderShirt(size) {
 switch(size) {
  case [ShirtSize.SMALL] :
   println "The size of the shirt is small"
   break;
  case [ShirtSize.MEDIUM] :
   println "The size of the shirt is medium"
   break;
  case [ShirtSize.LARGE] :
   println "The size of the shirt is large"
   break;
  case [ShirtSize.EXTRALARGE] :
   println "The size of the shirt is extra Large"
   break;
  default :
   println "The shirt size is not available"
   break;
 }
}

orderShirt(ShirtSize.MEDIUM)
orderShirt(ShirtSize.SMALL)
orderShirt(ShirtSize.LARGE)
orderShirt(ShirtSize.EXTRALARGE)
The output from the above code is as follows
The size of the shirt is medium
The size of the shirt is small
The size of the shirt is large
The size of the shirt is extra Large
The shirt size is not available
Java 5 enum allows you to define methods and constructors, The Groovy also support that features, as shown here.
enum ShirtSize {
 SMALL(36),MEDIUM(38),LARGE(40),EXTRALARGE(44)
 final int shirtSize
 ShirtSize(size) {
  shirtSize = size 
 }
 
 def printShirtDetails() {
  println "The size of ${this} is ${shirtSize} cm"
 }
}

for(shirts in ShirtSize.values()) {
 shirts.printShirtDetails()
}
The result from the above code is as follows.
The size of SMALL is 36 cm
The size of MEDIUM is 38 cm
The size of LARGE is 40 cm
The size of EXTRALARGE is 44 cm
Java enum allows you to override or redefine the method for specific values of enum. In Groovy you can't achieve this one directly, you can achieve through inject the method into instance using ExpandoMetaClass, as show here.
Java way for overriding or redefining method of enum variable. 
enum WeekEndActivity {
 SATURDAY {
  public String toString() {
   return "Play" ;
  }
 },
 SUNDAY {
  public String toString() {
   return "Relax";
  }
 };
}
public class EnumDemo {
 public static void main(String args[]) {
  System.out.println("Saturday activity : " + WeekEndActivity.SATURDAY);
  System.out.println("Sunday activity : " + WeekEndActivity.SUNDAY);
 }
}
The result from the above example is shown here. 
Saturday activity : Play
Sunday activity : Relax
Groovier way for implementing above example is shown here. 
enum WeekEndActivity {
 SATURDAY,SUNDAY
 def activity() {
  'Relax'
 }
}

def expandoMetaClass = new ExpandoMetaClass(WeekEndActivity)
expandoMetaClass.activity = { -> 'Play'}
expandoMetaClass.initialize()
WeekEndActivity.SATURDAY.metaClass = expandoMetaClass

for(day in WeekEndActivity.values()) {
 println "${day} - ${day.activity()}"
}
The result from the above example is shown here. 
SATURDAY - Play
SUNDAY - Relax
Labels:

Comments

Post a Comment

Popular posts from this blog

Ext JS 4 – Creating web page using Ext.container.Viewport class and region propery

The Ext.container.Viewport is used for creating general web page and region property is used for splitting web page into different parts. Ext.container.Viewport is a specialized container represents the viewable area of the application (the browser area). It render itself to the document body, there is no need for providing renderTo property and it automatically sizes itself to size of the browser viewport. The viewport also re-size the child elements based on view area(based on browser width and height). The default layout of the viewport is border layout and we can customize this property according to our requirements. The viewport does not provide any scrolling. If necessary, the child elements(generally panels) within viewport needs to provide a scroll feature by using autoScroll property. See the below example for better understanding. This is Home.js file placed into app/view folder. Ext.define('MyApp.view.Home', { extend : 'Ext.container.Viewport&#
4 comments
Read more

Getting servlet init parameter that is defined in web.xml

1. Create a new dynamic web project using eclipse. 2. Create a one new servlet and include the following code. package com.controller ; import java.io.IOException; import javax.servlet .ServletConfig; import javax.servlet .ServletException; import javax.servlet .annotation.WebServlet; import javax.servlet .http.HttpServlet; import javax.servlet .http.HttpServletRequest; import javax.servlet .http.HttpServletResponse; @ WebServlet ( "/LoginController" ) public class LoginController extends HttpServlet {                 private static final long serialVersionUID = 1L;                 public LoginController() {         super ();     }     protected void doPost( HttpServletRequest request, HttpServletResponse response) throws ServletException , IOException {                                 ServletConfig config = getServletConfig ();                                 System.out.println( "Init parameter user nam
1 comment
Read more

Simple Login Application Using Spring MVC and Hibernate – Part 1

 I hope developers working in web application development might hear about MVC architecture. Almost all technologies provide support for MVC based web application development, but the success is based on many factors like reusable of the code, maintenance of the code, future adaption of the code, etc..,  The success of the Spring MVC is “ Open for extension and closed for modification ” principle. Using Spring MVC the developers can easily develop MVC based web application. We don’t need any steep learning curve at the same time we need to know the basics of spring framework and MVC architecture. The Spring MVC consists of following important components. 1. Dispatcher servlet 2. Controller 3. View Resolver 4. Model Spring MVC - Overview  The overall architecture of Spring MVC is shown here.  1. When “Dispatcher Servlet” gets any request from client, it finds the corresponding mapped controller for the request and just dispatches the request to the corresponding contro
60 comments
Read more