{"id":3447,"date":"2019-06-20T11:43:24","date_gmt":"2019-06-20T11:43:24","guid":{"rendered":"http:\/\/softlect.in\/?p=3447"},"modified":"2019-06-20T12:01:28","modified_gmt":"2019-06-20T12:01:28","slug":"java-interfaces","status":"publish","type":"post","link":"http:\/\/softlect.com\/index.php\/java-interfaces\/","title":{"rendered":"Java Interfaces"},"content":{"rendered":"

<\/a>Interfaces<\/strong><\/h1>\n

 <\/p>\n

Using the keyword interface<\/strong>, you can fully abstract a class\u2019 interface from its implementation. That is, using interface<\/strong>, you can specify what a class must do, but not how it does it. Interfaces are syntactically similar to classes, but they lack instance variables, and their methods are declared without any body. Once it is defined, any number of classes can implement an interface<\/strong>. Also, one class can implement any number of interfaces. To implement an interface, a class must create the complete set of methods defined by the interface. How ever, each class is free to determine the details of its own implementation. By providing the interface <\/strong>keyword, Java allows you to fully utilize the \u201cone interface, multiple methods\u201d aspect of polymorphism. Interfaces are designed to support dynamic method resolution at run time. Normally, in order for a method to be called from one class to another, both classes need to be present at compile time so the Java compiler can check to ensure that the method signatures are compatible.<\/p>\n

<\/a>Defining an Interface<\/h2>\n

An interface is defined much like a class. This is the general form of an interface:<\/p>\n

 <\/p>\n

access <\/em>interface name <\/em>{<\/p>\n

return-type method-name1<\/em>(parameter-list<\/em>);<\/em><\/p>\n

return-type method-name2<\/em>(parameter-list<\/em>);<\/em><\/p>\n

type final-varname1 = value;<\/em><\/p>\n

type final-varname2 = value;<\/em><\/p>\n

\/\/ …<\/em><\/p>\n

return-type method-nameN<\/em>(parameter-list<\/em>);<\/em><\/p>\n

type final-varnameN = value;<\/em><\/p>\n

}<\/p>\n

 <\/p>\n

Here, access <\/em>is either public <\/strong>or not used. When no access specifier is included, then default access results, and the interface is only available to other members of the package in which it is declared. When it is declared as public<\/strong>, the interface can be used by any other code. name <\/em>is the name of the interface, and can be any valid identifier. Notice that the methods which are declared have no bodies. They end with a semicolon after the parameter list. They are, essentially, abstract methods; there can be no default implementation of any method specified within an interface. Each class that includes an interface must implement all of the methods. Variables can be declared inside of interface declarations. They are implicitly final <\/strong>and static<\/strong>, meaning they cannot be changed by the implementing class. They must also be initialized with a constant value. All methods and variables are implicitly public <\/strong>if the interface, itself, is declared as public<\/strong>. Here is an example of an interface definition. It declares a simple interface which contains one method called callback( ) <\/strong>that takes a single integer parameter.<\/p>\n

 <\/p>\n

interface Callback {<\/p>\n

void callback(int param);<\/p>\n

}<\/p>\n

<\/a>Implementing Interfaces<\/h2>\n

Once an interface <\/strong>has been defined, one or more classes can implement that interface. To implement an interface, include the implements <\/strong>clause in a class definition, and then create the methods defined by the interface. The general form of a class that includes the implements <\/strong>clause looks like this:<\/p>\n

 <\/p>\n

access <\/em>class classname <\/em>[extends superclass<\/em>]<\/p>\n

[implements interface <\/em>[,interface…<\/em>]] {<\/p>\n

\/\/ class-body<\/p>\n

}<\/p>\n

 <\/p>\n

Here, access <\/em>is either public <\/strong>or not used. If a class implements more than one interface, the interfaces are separated with a comma. If a class implements two interfaces that declare the same method, then the same method will be used by clients of either interface. The methods that implement an interface must be declared public<\/strong>. Also, the type signature of the implementing method must match exactly the type signature specified in the interface <\/strong>definition. Here is a small example class that implements the Callback <\/strong>interface shown earlier.<\/p>\n

 <\/p>\n

class Client implements Callback {<\/p>\n

\/\/ Implement Callback’s interface<\/p>\n

public void callback(int p) {<\/p>\n

System.out.println(“callback called with ” + p);<\/p>\n

}<\/p>\n

}<\/p>\n

 <\/p>\n

Notice that callback( ) <\/strong>is declared using the public <\/strong>access specifier. When you implement an interface method, it must be declared as public<\/strong>. <\/em>It is both permissible and common for classes that implement interfaces to define additional members of their own. For example, the following version of Client <\/strong>implements callback( ) <\/strong>and adds the method nonIfaceMeth( )<\/strong>:<\/p>\n

 <\/p>\n

class Client implements Callback {<\/p>\n

\/\/ Implement Callback’s interface<\/p>\n

public void callback(int p) {<\/p>\n

System.out.println(“callback called with ” + p);<\/p>\n

}<\/p>\n

void nonIfaceMeth() {<\/p>\n

System.out.println(“Classes that implement interfaces ” +<\/p>\n

“may also define other members, too.”);<\/p>\n

}<\/p>\n

}<\/p>\n

<\/a>Accessing Implementations through Interface References<\/h3>\n

 <\/p>\n

You can declare variables as object references that use an interface rather than a class type. Any instance of any class that implements the declared interface can be referred to by such a variable. When you call a method through one of these references, the correct version will be called based on the actual instance of the interface being referred to. This is one of the key features of interfaces. The method to be executed is looked up dynamically at run time, allowing classes to be created later than the code which calls methods on them. The calling code can dispatch through an interface without having to know anything about the \u201ccallee.\u201d This process is similar to using a superclass reference to access a subclass object, as described earlier. The following example calls the callback( ) <\/strong>method via an interface reference variable:<\/p>\n

 <\/p>\n

class TestIface {<\/p>\n

public static void main(String args[]) {<\/p>\n

Callback c = new Client();<\/p>\n

c.callback(42);<\/p>\n

}<\/p>\n

}<\/p>\n

 <\/p>\n

The output of this program is shown here:<\/p>\n

callback called with 42<\/p>\n

 <\/p>\n

Notice that variable c <\/strong>is declared to be of the interface type Callback<\/strong>, yet it was assigned an instance of Client<\/strong>. Although c <\/strong>can be used to access the callback( ) <\/strong>method, it cannot access any other members of the Client <\/strong>class. An interface reference variable only has knowledge of the methods declared by its interface <\/strong>declaration. Thus, c <\/strong>could not be used to access nonIfaceMeth( ) <\/strong>since it is defined by Client <\/strong>but not Callback<\/strong>. While the preceding example shows, mechanically, how an interface reference variable can access an implementation object, it does not demonstrate the polymorphic power of such a reference. To sample this usage, first create the second implementation of Callback<\/strong>, shown here:<\/p>\n

 <\/p>\n

\/\/ Another implementation of Callback.<\/p>\n

class AnotherClient implements Callback {<\/p>\n

\/\/ Implement Callback’s interface<\/p>\n

public void callback(int p) {<\/p>\n

System.out.println(“Another version of callback”);<\/p>\n

System.out.println(“p squared is ” + (p*p));<\/p>\n

}<\/p>\n

}<\/p>\n

 <\/p>\n

Now, try the following class:<\/p>\n

 <\/p>\n

class TestIface2 {<\/p>\n

public static void main(String args[]) {<\/p>\n

Callback c = new Client();<\/p>\n

AnotherClient ob = new AnotherClient();<\/p>\n

c.callback(42);<\/p>\n

c = ob; \/\/ c now refers to AnotherClient object<\/p>\n

c.callback(42);<\/p>\n

}<\/p>\n

}<\/p>\n

 <\/p>\n

The output from this program is shown here:<\/p>\n

callback called with 42<\/p>\n

Another version of callback<\/p>\n

p squared is 1764<\/p>\n

 <\/p>\n

As you can see, the version of callback( ) <\/strong>that is called is determined by the type of object that c <\/strong>refers to at run time. While this is a very simple example, you will see another, more practical one shortly.<\/p>\n

<\/a>Partial Implementations<\/h3>\n

If a class includes an interface but does not fully implement the methods defined by that interface, then that class must be declared as abstract<\/strong>. For example:<\/p>\n

 <\/p>\n

abstract class Incomplete implements Callback {<\/p>\n

int a, b;<\/p>\n

void show() {<\/p>\n

System.out.println(a + ” ” + b);<\/p>\n

}<\/p>\n

\/\/ …<\/p>\n

}<\/p>\n

 <\/p>\n

Here, the class Incomplete <\/strong>does not implement callback( ) <\/strong>and must be declared as abstract. Any class that inherits Incomplete <\/strong>must implement callback( ) <\/strong>or be declared abstract <\/strong>itself.<\/p>\n

<\/a>Interfaces Can Be Extended<\/h2>\n

One interface can inherit another by use of the keyword extends<\/strong>. The syntax is the same as for inheriting classes. When a class implements an interface that inherits another interface, it must provide implementations for all methods defined within the interface inheritance chain. Following is an example:<\/p>\n

 <\/p>\n

\/\/ One interface can extend another.<\/p>\n

interface A {<\/p>\n

void meth1();<\/p>\n

void meth2();<\/p>\n

}<\/p>\n

\/\/ B now includes meth1() and meth2() — it adds meth3().<\/p>\n

interface B extends A {<\/p>\n

void meth3();<\/p>\n

}<\/p>\n

\/\/ This class must implement all of A and B<\/p>\n

class MyClass implements B {<\/p>\n

public void meth1() {<\/p>\n

System.out.println(“Implement meth1().”);<\/p>\n

}<\/p>\n

public void meth2() {<\/p>\n

System.out.println(“Implement meth2().”);<\/p>\n

}<\/p>\n

public void meth3() {<\/p>\n

System.out.println(“Implement meth3().”);<\/p>\n

}<\/p>\n

}<\/p>\n

class IFExtend {<\/p>\n

public static void main(String arg[]) {<\/p>\n

MyClass ob = new MyClass();<\/p>\n

ob.meth1();<\/p>\n

ob.meth2();<\/p>\n

ob.meth3();<\/p>\n

}<\/p>\n

}<\/p>\n

 <\/p>\n

Any class that implements an interface must implement all methods defined by that interface, including any that are inherited from other interfaces.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Interfaces   Using the keyword interface, you can fully abstract a class\u2019 interface from its implementation. That is, using interface, you can specify what a class must do, but not… <\/p>\n","protected":false},"author":1,"featured_media":3472,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[83],"tags":[],"aioseo_notices":[],"amp_enabled":true,"_links":{"self":[{"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/posts\/3447"}],"collection":[{"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/comments?post=3447"}],"version-history":[{"count":2,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/posts\/3447\/revisions"}],"predecessor-version":[{"id":3486,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/posts\/3447\/revisions\/3486"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/media\/3472"}],"wp:attachment":[{"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/media?parent=3447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/categories?post=3447"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/softlect.com\/index.php\/wp-json\/wp\/v2\/tags?post=3447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}