Skip to main content

Java Enum in 10 Minutes

This tutorial aims at teaching Java enums to newbies in 10 mins. To meet this goal I will keep my descriptions short and concise. References will be provided at the end of the tutorial for detailed study.

  • Concept 1 : Enums are introduced in Java 1.5 and are used to define constants.

Scenario 1: Defining Constants
public enum WeekDay{
    MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY,
    SUNDAY;
}


Usage
    WeekDay  day =  WeekDay.THURSDAY;
  1. System.out.println(day); --> Will print THURSDAY
  2. if(day == WeekDay.THURSDAY) { // do something }
  3. switch(day){ case MONDAY : //do something e.t.c}
  4. public void someMethod(WeekDay day){//do something with day}

  • Concept 2 : An Enum can be considered to be like a class and the constants in the enum can be considered to be instances (objects) of the class.
  • Concept  3: An Enum's constructor should always be private if not compile time error will be thrown.

Scenario 2: Defining Constants with a value and methods inside enums
public enum Level {
    MIN(10), MEDIUM(50), MAX(100);

    private int value;
    private Level(int value){
        this.value = value;
    }

   public int getValue(){ return value; }
}

In the above example, when an enum is created,  the private constructor is called and the value mentioned in the constant will be passed and stored in the int variable. The user has no way of changing the value thenceforth.

Usage
Level level = Level.MIN;
  1. System.out.println(level); --> Will Print MIN (to get MIN : 10 one alternative is to override the "toString()" method in the enum)
  2. System.out.println(level+":"+level.getValue()); --> we are calling a method on the enum here, this will output MIN:10

  • Concept 4 : Enums can implement interfaces and have abstract methods defined in them.
Scenario 3: Enums implementing interfaces and declaring abstract methods.

public interface SillyInterface{ public String saySomethingSilly();}

enum Advanced implements SillyInterface{
    //Each constant of the enum can be considered to be an instance of the class.
    //Each instance has to therefore implement abstract methods defined as well as override methods of
    //any interface that gets implemented.
    Funny("Jim Carry") {
        @Override
        String sayDialogue() {
            return "Did you miss meeeeeeeeeeeeeeeeee";
        }
        public void saySomethingSilly(){return this.getName()+" says some silly
        thing";}
    },
    BAD("Gabbar Singh") {
        @Override
        String sayDialogue() {
            return "Kitne Aadmi the";
        }
     public void saySomethingSilly(){return this.getName()+" says some silly
     thing";}
    };
    private String name;
    private advanced(String name){
        this.name = name;
    }
    public String getName(){
        return name;
    }
    //This abstract method has to be implemented by each instance of the enum.
    abstract String sayDialogue();
}

Thats it. Now you know most of the enum related details.

References:





Comments

arjun said…
Very nice article and ref list, I would like to share my references too
http://www.javaworld.com/javaworld/javatips/jw-javatip122.html
http://tutiez.com/enum-in-java-with-java-enum-examples.html
http://chaoticjava.com/posts/tricks-with-enums/
Thanks Arjun for sharing these links.

Popular posts from this blog

Openstack : Fixing Failed to create network. No tenant network is available for allocation issue.

Assumptions : You are using ML2 plugin configured to use Vlans If you try to create a network for a tenant and it fails with the following error: Error: Failed to create network "Test": 503-{u'NeutronError': {u'message': u'Unable to create the network. No tenant network is available for allocation.', u'type': u'NoNetworkAvailable', u'detail': u''}} The problem can be due to missing configuration in the below files: In /etc/neutron/plugins/ml2/ml2_conf.ini network_vlan_ranges =physnet1:1000:2999 (1000:2999 is the Vlan range allocation) In /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini bridge_mappings = physnet1:br-eth1 (in OVS we map the physical network to the OVS bridge) Note You should have created a bridge br-eth1 manually and mapped it to a port ovs-vsctl add-br br-eth1 ovs-vsctl add-port br-eth1 eth1 Once configuration is done, restart the neutron ovs agent on the compute node(s):

Solved: Fix for Git clone failure due to GnuTLS recv error (-9)

My devstack installation was failing with an error reported by the GnuTLS module as shown below: $ git clone https://github.com/openstack/horizon.git /opt/stack/horizon --branch master Cloning into '/opt/stack/horizon'... remote: Counting objects: 154213, done. remote: Compressing objects: 100% (11/11), done. error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed The following Git config changes fixed the issue for me. Am hoping it will be useful for someone out there: $ git config http.sslVerify false $ git config --global http.postBuffer 1048576000

QuickBite: Tap Vs Veth

Linux supports virtual networking via various artifacts such as: Soft Switches (Linux Bridge, OpenVSwitch) Virtual Network Adapters (tun, tap, veth and a few more) In this blog, we will look at the virtual network adapters tap and veth. From a practical view point, both seem to be having the same functionality and its a bit confusing as to where to use what. A quick definition of tap/veth is as follows: TAP A TAP is a simulated interface which exists only in the kernel and has no physical component associated with it. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a user space program (in our case the VM) gets attached to the tap interface it gets hold of a file descriptor, reading from which gives it the data being sent on the tap interface. Writing to the file descri