Welcome!

Java Authors: Jason Bloomberg, Elizabeth White, Liz McMillan, Roger Strukhoff, Pat Romanski

Related Topics: Java

Java: Article

Methods, Constructors, Overloading and Access Levels

Lesson 3

Methods tell us what a class can do.Developers can define their own methods and Java Developers Kit has a variety of classes and each of them may contain methods. Some methods require arguments - the incoming data that have to be processed. For example, here is the code to convert a String value to a number of the type of integer:

String testStr = "5000"; int test = Integer.parseInt(testStr);

It is said that the method parseInt() has one argument of type String.

The method parseInt() is defined in the Java class Integer. Programmers could also define methods that take arguments, for example:

double calcTax(double grossIncome, String state,  
              int dependents){
 // The code implementing business logic goes here
}

Arguments are used in the method body the same way as if they were declared as local variables, but their values will be provided by the caller of the method, for example:

double myTax = calcTax(45000.00, "NJ", 2);

The 45000.00, "NJ", and 2 are provided by the caller of the method calcTax().

Special Methods: Constructors

One of the most widely used ways of creating an instance of a class is the operator new, for example:

Tax t = new Tax();

During the process of the class instantiation a special method called constructor will be called automatically. In our example parentheses after the word Tax mean that a constructor with no arguments will be called by the Java Virtual Machine (JVM).

Constructors have the following characteristics:

  • They are called only once when the class is being instantiated.
  • They must have the same name as the class itself.
  • They do not return a value and you do not have to specify the keyword void.

A class can have more than one constructor (see the section "Method Overloading" below).

If you do not create a constructor for the class, Java helps you by using a so called default no-argument constructor. That's why the Java compiler does not complain about the statement new Tax(), even though we have not defined any constructor for the class Tax.

Constructors are usually used to assign initial values to member variables of the class, for example:

class Tax {
  double grossIncome;   // member variables
  String state;
  int dependents;
   
  Tax (double gi, String st, int depen){
    grossIncome = gi;  // member variable initialization
    state = st;
    dependents=depen;
  }
  ...
}

If a constructor with arguments has been defined in a class, you can no longer use a default no-argument constructor - you have to write write one.

Besides the operator new, you can create an instance of the class by loading the class first and then calling the method newInstance() which will also executes constructor's code:

Class.forName("Tax").newInstance();

The Keyword this

The keyword this is useful when you need to refer to an instance of the class from its method. Let's consider an example:
class Tax {
   double grossIncome;
   Tax(double grossIncome){
     this.grossIncome = grossIncome;
   }
}

The keyword this helps avoid name conflicts, for example this.grossIncome refers to a member variable grossIncome, while the grossIncome on the right refers to the argument's value.

Let's look at another example - say you have some class with a method verifyTax( Tax t) that needs an instance of class Tax as an argument. This is how you can call it from the class Tax:

class Tax {
  void myMethod(){
    ...
    SomeOtherClass s = new SomeOtherClass();
    s.verifyTax(this);
  }
}

Method Overloading

If a class has more than one method with the same name, but with different argument lists, it's called method overloading. For example, the method print() could be called with different types of arguments. Actually there are multiple overloaded versions of the method print(), it's just easier to remember one method print(), than printString(), printInt(), etc.

Constructors also can be overloaded.

The next version of our class Tax will have two overloaded constructors: one with 3 arguments (income, state and dependents), and another one with 2 (income and state). If the 2-argument constructor will be used when the class is instantiated, the default value of 1 dependent is assumed.

class Tax {
  double grossIncome;
  String state;
  int dependents;
   
  Tax (double gi, String st, int depen){
    grossIncome = gi;
    state = st;
    dependents=depen;
  }

  Tax (double gi, String st){
    grossIncome = gi;
    state  = st;
    dependents=1;   // Default value 
  }
  ...
}

Only one constructor will be used when a class is instantiated, based on the provided argument list. The example below uses the 3-arguments constructor:

Tax t = new Tax( 50000.00, "NJ", 2);

The following example uses 2-argument constructor:

Tax t = new Tax( 50000.00, "NJ");

The keyword super

The keyword super is used to refer to the superclass of an object, for example it could be used to call a constructor of the superclass:
class  NJTax extends Tax{
   NJTax(double income, String state){
    super(income, state, 1);
    ...
  }
}

The keyword super could also be used to call any method in the superclass. You do not usually use it, because methods of the superclass are available just by specifying their names. Having an overridden method could come in handy - one in the current class and the other one in the superclass. If for any reason you want to call a particular method from a superclass, even though there is a method with the same signature in the subclass, do it as follows:

super.myMethod();

Access Levels

Java classes, methods and member variables could have public, private, protected and package access levels, for example:
public class Tax {
   private double grossIncome; 
   private String state;
   private int dependents;
   protected double calcTax(…) {…}
}

The keyword public means that this element (class, method or a variable) could be accessed from any other Java class.

The keyword protected makes the element "visible" either from the current class, or from it's subclasses.

The keyword private is the most restrictive one and makes the member variable or a method available only within the current class. For example, our class Tax may need some additional internal method that could be called from the method calcTax(). Descendents of the class Tax do not need to know about it and this method should be declared as private.

If you do not specify any access level, a default (package) access level is used.

One of the main features of object-oriented languages is encapsulation, which is an ability to hide and protect its elements. The classes should expose to their possible users only the necessary methods, i.e. alcTax(). The methods that the class Tax exposes to its prospective clients could be called Application Program Interface (API).

Do you really know what exactly happens under the hood when you start you car's engine? Do you really want to know? That ignition key slot and the "Check oil" signal are example of your car's API.

If you are not sure which access level to give to methods or variables, just make them all private. If at the later development stage another class needs to access them, you can always change it, but this is a simple way to protect all the internal of your application from misuse. Think of it this way: "I want to sell my class Tax to various accounting firms across the country. If software developers of these firms will incorporate this class into existing systems - what's the minimum number of methods that they must know about to be able to calculate a tax"? If car designers would not ask themselves a similar question, you'd need to press hundreds of buttons just to start the engine.

More Stories By Yakov Fain

Yakov Fain is a co-founder of two software companies: Farata Systems and SuranceBay. He authored several technical books and lots of articles on software development. Yakov is Java Champion (https://java-champions.java.net). He leads leads Princeton Java Users Group. Two of Yakov's books will go in print this year: "Enterprise Web Development" (O'Reilly) and "Java For Kids" (No Starch Press).

Comments (8) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Dave J 02/10/04 11:43:40 AM EST

>During the process of the class instantiation...
>"Constructors have the following characteristics:
>They are called only once when the class is being >instantiated."

Should read:
"During the process of the object instantiation..."
Classes are not instantiated!*. You should not confuse objects with classes - Your confusion can cause alot of harm when writing such articles.

*In OO languages like smallltalk where everthing is an object classes are in fact objects - but even then they are refered to as meta-objects.In java classes are loaded.

Tim Lambert 12/22/03 09:23:25 AM EST

As a web article I don''t have a problem with it. And as such I retract my previous comments.

My initial thought was this that this article was going to wind up in the printed publication which has precious limited column space. And IMO should be reserved for articles of interest to actual Java developers. After all that''s (part of) the name of the publication.

John Saccoccio 12/22/03 09:02:54 AM EST

If you''re miles above this article, you probably can''t spare the time to mentor someone. Do them a favor and forward this article to them. I certainly hope there are others out there climbing the Java learning curve. Having done so myself in 1999 feeling surrounded by a group of selfish xenophobic primadonnas (a programmer personality profile it took a long time to get over), I welcomed this type of tutorial for it''s clarity and lack of a condescending attitude. In the end, it was Bruce Eckel''s ''Thinking in Java'' that breezed me through the certification exam.

Jason Bell 12/20/03 03:54:55 AM EST

This is to Tim Lambert

The short answer to your question is, "yes".

The slightly longer answer is: I think we have a right to train, encourage and empower developers at ALL levels. From personal experience the only way I could get information on learning Java was on the net and looking at, what are now, early copies of JDJ.

I understand your point of view but JDJ is for the entire community and not just focused on seasoned developers (though you guys are very important). We receive article proposals at all levels. My previous editorials have been quite strong on the learning element, encouraging developers to train and mentor other developers. I believe we all have something to share that could be a benefit to someone else.

Tim, if you don''t mind me asking. What sort of articles are you looking for? User feedback from the web site and the print publication are always welcome.

As a final note, Scott McNealy said that Sun''s target was 10 Million developers. These developers need to start somewhere and I think here is a good place to start.

Kind regards
Jason Bell
Core and Internals Editor: Java Developers Journal

Yakov Fain 12/19/03 10:31:21 PM EST

Lambert,

JDJ has readers of all levels.

Please take a look at the following URL:

http://www.sys-con.com/story/category.cfm?id=276

During the last month more than 900 people read the article
called "Your First Java program".

I''ll be happy if more and more people will learn and start using Java. I might dissapoint you even more, but currently I''m writing a book on Java programming for kids. In this book I''m explaining how to create a class Pet and its subclass Fish. Sorry...

Tim Lambert 12/19/03 08:47:21 PM EST

You''ve got to be kidding.

Is the target audience of JDJ people who have no clue about the very basics of Java?

How about probing some topics that are of interest to the professional Java developer.

Yakov Fain 12/19/03 09:24:11 AM EST

You''re absolutely right, but this series of articles is written as a tutorial, and Java packages were not explained yet. But I do promise to tell the whole truth about protected access level in one of the future articles.

ultrix 12/19/03 04:15:19 AM EST

The keyword protected makes the element "visible" either from the current class, or from it''s subclasses.

that''s not the whole truth - the elememts are visible from the classes in the same package as well