Abstraction v/s Encapsulation

Java is an Object Oriented Programming language. Each object oriented programming language is standing on the following pillars.

A. Polymorphism

B. Abstraction

C. Inheritance

D. Encapsulation

Now everyone who deals with Java code, surely understands inheritance and they have  a fair idea about polymorphism. Everyone knows inheritance because Java has forced developers to use inheritance. Each class inherits Object class internally. That is the reason we all understand Inheritance.

Polymorphism, is little more complex and less used concept. There are possibilities that developer may code thousand lines without encountering necessity of polymorphism in his code.

Abstraction and encapsulation are least used principle in Java programming language. Usually a beginner could not understand the analogy behind abstraction whereas  a beginner uses encapsulation logic by default. So we never try to explore these concepts until one fine day an interviewer asks the difference between Abstraction and Encapsulation. Seriously we should take interviews to increase our knowledge about technology.

If we need to define these principle's in two words then we can say Abstraction is implementation hiding where as encapsulation is Data Hiding.

What is Abstraction?

Class's definition is not complete and undefined definition is completed by child classes.

Weird, is not it? When there is no scope of creating a class then why having such class?

Database drivers are best example to illustrate abstraction. JDBC has defined a set of abstract interfaces/ abstract classes. Database providers have to complete the implementation for the following interfaces and classes. Now to interact with one database, developer need to register respective driver without changing the code. Developer does not need to mug up multiple databases to code for each of them. So using abstraction, problem of tackling different databases has been handled brilliantly. So without disclosing the actual implementation, desired functionality has been achieved.

What is Encapsulation?

Data is not directly accessible to user. It is much safer and recommended to make all fields as private and provide field accessors ( getter and setter methods ). Private is used so that no one could destroy the data intentionally and unintentionally and accessors methods provide more flexibility and control over the field.

Let's try to understand this with Walmart stores located in different countries. Let's say Walmart is trying to sell one product across countries. So for each country it will be inappropriate to have different instance of same product. To save the price of product they need to convert the price while storing and displaying, so having getter and setter methods give the control on data.

Here is the little difference between the use of abstraction and encapsulation. Hope I am able to clarify a little about complex and important concept of core Java.

Object Oriented Programming Part 2

In earlier post we have already discovered Object oriented programming, orientation, its fundamentals and features. Here we will take up next remaining questions.

These are the questions whose answer are we seeking here in these blogs…

ü  What is Object Oriented Programming?

ü  What are the fundamental concepts/Features of OOP?

ü  What is Object Based Programming?

ü  What is Procedural programming?

ü  What are the features of Procedural programming?

ü  Compare basic features of the OOP and PP?

First 2 questions have already been answered in the first blog. Here I will start with the third question.

What is Object Based Programming?

Object based programming is associated with objects, objects which consist fields and methods similar to OOP. In object based programming few features(Abstraction, Polymorphism, Encapsulations, Inheritance) of OOP are included. It is not wrong to say, OBP is a subset of OOP where subset has all the features except few.

As I am not concentrating more on this paradigm so I am not going to invest much of your time here.

What is Procedural programming?

In Procedural programming instead of data; structure of the program is the determining feature. Here programmer concentrate on structure of the program instead the behaviour and state of the object.

Edsger Dijkstra's structured programming, where the logic of a program is a structure composed of similar sub-structures in a limited number of ways. This reduces understanding a program to understanding each structure on its own, and in relation to that containing it, a useful separation of concerns.

At low level. structure programming composed of simple, hierarchical program flow structures. These are Sequence(Ordered sequence of statements), selection (Decision making conditions) and repetition(repetitive statements).

In current scenario Fortron, Basic are using structured programming. Branch of structures programming used by Procedural programming which is implemented in C.

Procedural programming is a branch of structural programming where procedure are created on the basis of structures. Procedures are routines, subroutines, functions and their sequence.

What are the features of Procedural programming?

As stated above the poles of the procedural programming are methods, modules, functional calls, variables whereas procedural programming does not have features like abstraction, encapsulation, inheritance and polymorphism.

Methods: These can be understand as the basic feature. We create the structure of the program, divide it into sequence, selection, repetition and accordingly divide one routine to different subroutines and achieve the desired functionality.

Modules: n number of subroutines creates a module where all subroutines are scope specific.

functional calls: As oops uses messages pass between object here it is achieved by functional calls.

Variables: As PP does not belong to object, so each routine has its own variables associated with function’s scope.

Compare basic features of the OOP and PP?

Till now it is understood that Procedure based programming is much closer to deal with structure on the other side OOP only deals with objects, and blueprint of the objects.

Pros and Cons of PP: Procedure based programs tends to run quickly and use system resources efficiently. Whereas the drawback is that it does not fir gracefully with certain type of problems, such as in this paradigm programmer is forced to use structure approach to reach to the conclusion.

Pros and Cons of OOP: OOP is very similar to the perception of world, so it is less difficult to visualize things there. Code reuse is another big advantage of OOPS which is one among the hard hitting drawbacks of PP. OOP is runtime inefficient. It needs more memory and resource to run the program.

If we summarize the whole story, it is evident that none of the paradigm is inferior or superior. It is just our requirements which makes one preferred to us. To finalize the paradigm there are few factors which should be taken into account. First we should look for the data structure of the problem and accordingly should decide the paradigm. Benchmarking is another aspect which effects mostly testing efforts a lot. These 2 factors could highlight the preferences of selecting the programming structure.

I will take a break now. Again I am open to discussions, please post me your queries in comments.

Disclaimer: All the material here is the result of research and understanding of other material. If there is some content which is either incorrect or inappropriate to the context of the article I am always open for discussion.

Marker Interface

This post is not in the continuation of the last post. But this week I was searching about the marker interfaces. So I thought of documenting my learning about Marker Interfaces.

As it is known, Java interface defines contract between real world and objects, which implies when a class in implementing a java interface it has to implement all the methods defined in the interface.

What is a marker interface?

Marker interface is an interface which does not have any field and method associated with it.

/** 

* This interface is a marker interface. 

* For JVM it is just another interface without any method and field.

*/

public interface MarkerInterface {

}

Here as in the example above there is an interface which do not define any method and field. But this interface will compile without any issues.
/**

* MarkedClass is implementing MarkerInterface, 

* which means class MarkedClass is associated with MarkerInterface.

* This class will compile without any issues.

* */

public class MarkedClass implements MarkerInterface{

}

As mentioned in the example MarkedClass has been tagged as a MarkerInterface.
To compile this example you can copy the interface’s code to MarkerInterface.java file and copy class’s code to MarkedClass.java file.

What is the actual use of marker interfaces? Why will I prefer marker interface instead of an interface which has some methods?

Purpose of marker interfaces is to create a special type of Object, in such a way to restrict the classes that can be cast to it without placing ANY restrictions on the exported methods that must be provided. In another way these are used to provide metadata information to the classes.

To explain it further we can use an example…
There are quite a few IT organizations which primarily concentrate on product whereas there services are limited to their products and beside these organizations there are organizations which concentrate on services of the others products. These are classified as Product Organization and service organization.
A product company may sell their products either to Customer directly or to Service Company.  On the basis of the type of customer a product company wants to provide different set of contracts with the company. In general a product company has millions of customers and few service companies associated with it. So to distinguish between these two types of organization we mark Service companies with the marker interface.

This organization interface defines the contract.

/**

* This interface will have common utility methods that will be used across all the 

* customer as well as service organizations.  

*/ 

public interface Organization {

      String[] getProduct();     

      void setProduct(String[] products);

      //Many other such methods.      

}

This ServiceOrganization interface is a marker interface which will state the organization as a service organization.

/**
This interface is to mark an Organization as a Service Organization.

**/

public interface ServiceOrganization extends Organization{

}

Here you can see customer is implementing Organization, i.e. it is stating this Customer is not a special customer to me.
/**

* Customer is implementing Normal organization.

*/

public class Customer implements Organization {

@Override

public String[] getProduct() {

return null;

}

@Override

public void setProduct(String[] products) {

}

}

Now ServiceOrganization interface has been implemented by the Service customer class which will distinguish service customer from normal customer.
/**

* Service Customer has been tagged as service Organization but it does not need 

* to implement something other than method which will be defined by a

* common customer. 

*/

public class ServiceCustomer implements ServiceOrganization {

@Override

public String[] getProduct() {

return null;

}

@Override

public void setProduct(String[] products) {

}

}

As both types of customers have been separated with the use of marking, now it is not difficult to judge the customers.
Does Java have by default marker interface? If Yes, what all marker interfaces are there and what are their uses?
Yes, Java has few marker interfaces. Those are as follows:

java.util.RandomAccess

java.io.Serializable

java.rmi.Remote

java.util.EventListner

java.lang.Clonable

java.io.Serializable
When a class is implementing this interface this internally suggests to JVM that object of this class may be serialized for persistence purposes.
Source code for the interface is as mentioned below.
public interface Serializable {
}

So it is clear, writeObject and readObject methods are not part of the interface, but rather part of the serialization process, and help determine how to serialize an object.
java.lang.Clonable
Clonable interface is necessary to use clone method associated with each object. If clone is used without implementing clonable interface the code will throw a runtime exception.
java.util.EventListner
This interface also does not have any specific method but it is necessary for a class to implement the interface to achieve the functionality of listening the events.
java.util.RandomAccess
Implementing this interface suggests data accessing in the list is fast. So it is just marking list as fast random access. 
java.rmi.Remote
The remote interface serves to identify interfaces whose methods may be invoked from a non-local virtual machine. Any object that is a remote object must directly or indirectly implement this interface. Only those methods specified in a "remote interface", an interface that extends java.rmi.Remote are available remotely.
Here again marker interface has made sure if something has to access remotely then it should be marked with remote interface.
List of marker interfaces is long but the interfaces mentioned above are the widely known interfaces.

Like me You must be wondering, this all is fine but still there is one important question.
How does JVM deal with specific functionality of each marker interfaces?
I could not find something very specific to this question. But as most of the experts suggests Java does not do anything specific to identify the marker interface. instanceOf operator is used to identify whether the functionality is supported for the object or not.

If you look at the code of ObjectOutputStream.java, it is quite clear when serialization is supported by java.
//Piece of code of method - writeObject0(Object obj, boolean unshared){

.............

} else if (cl.isArray()) {

writeArray(obj, desc, unshared);

} else if (obj instanceof Serializable) {

writeOrdinaryObject(obj, desc, unshared);

} else {

throw new NotSerializableException(cl.getName());

}

.................

Now it is clear what are marker interfaces and at what instances do we use them. Java 5 release sun has introduced annotations, a way which will replace marker interface in future designs. Annotations are more descriptive and powerful mechanism to tag a class. I will talk about annotations in coming blogs..
Disclaimer: All the material here is the result of research and understanding of other material. If there is some content which is either incorrect or inappropriate to the context of the article I am always open for discussion.