Home > Articles > Programming > Java

  • Print
  • + Share This
Like this article? We recommend

Late binding

The secret to understanding binary compatibility is to understand late binding. Late binding means that Java looks at the names of classes, fields, and methods at runtime. That's unlike most C/C++ compilers, which remove the names and replace them with numerical offsets. It's the reason that binary compatibility works in Java.

With late binding, method names, field names, and class names are resolved at run time. That means that you can provide any class you like, as long as the names (and types) of its fields and methods are identical. There are other rules about access (private, public, etc.) and abstract-ness (you can't call a method that isn't really there), but late binding is the heart of binary compatibility.

You can use late binding to try to confuse the JVM. For example, if you start with these classes:

class Tinker 	
{
}
class Evers extends Tinker
{
}
class Chance extends Evers
{
}

In a different directory (or another computer), create different versions of Tinker and Chance:

class Tinker extends Chance	
{
  System.out.println("Double play!");
}
class Chance 
{
}

These two sets of code compile independently. But if you take version 1 of Evers and Chance, and version 2 of Tinker, you get:

Figure xxx

Really, Chance refers to two different things in versions 1 and 2. But when you mix and match the code, late binding means that the two versions appear to be the same.

Obviously this would be a violation in Java, but Java compiler gets no say in the matter: we're just putting together three class files that worked independently. However, this breaks binary compatibility, and you get this error:

java.lang.ClassCircularityError: Tinker

When you try to create an instance of Tinker, you get:

java.lang.ClassCircularityError: Tinker

This example may seem trivial and silly, but it's not all that hard to accidentally introduce circularities or other binary incompatibilities. It's easy to re-implement a class (for performance reasons, or because you lost the source code, or because you didn't like the way it was written the first time) and leave something out.

But conversely, once you understand the rules, you can substantially re-implement classes without disturbing the other binaries, with all the advantages we talked about in the first issue of this article.

For example, let's start out with the bare outlines of a couple of related E-mail programs we'll call FrodoMail and SamMail:

abstract class Message implements Classifiable
{
}
class EmailMessage extends Message
{
  public boolean isJunk() { return false; }
}

interface Classifiable
{
  boolean isJunk();
}
class FrodoMail
{
  public static void main(String a[])
  {
	Classifiable m = new EmailMessage();
	System.out.println(m.isJunk());
  }
}
class SamMail
{
  public static void main(String a[])
  {
	EmailMessage m = new EmailMessage();
	System.out.println(m.isJunk());
  }
}

I can choose to reimplement Message without Classifiable:

class Message
{
}

and SamMail will continue to run just fine. However, FrodoMail will throw an exception:

java.lang.IncompatibleClassChangeError
	at FrodoMail.main

That's because SamMail never depended on an EmailMessage being Classifiable, but FrodoMail did. The binary of FrodoMail mentions the Classifiable interface, by name. The methods for Classifiable are still there, but because the class doesn't name the interface anymore, it's a Classifiable as far as the JVM is concerned.

Other common causes of binary incompatibility include:

  • Changing a method from static to non-static (or vice versa) (IncompatibleClassChangeError)

  • Changing a member (field or method) to be private (IllegalAccessError)

  • Changing a class to be abstract (IncompatibleClassChangeError)

  • Changing a method to be abstract (AbstractMethodError)

  • Removing a field (NoSuchFieldError)

  • Removing an interface (IncompatibleClassChangeError)

IncompatibleClassChangeError is the root of most of the exceptions you'll see caused by incompatible binaries. The ClassCircularityError is actually a sister class to IncompatibleClassChangeError. Both are subsumed by LinkageError, which reports the sorts of errors caused by altering a class without recompiling, as well as other kinds of errors that occur when a class is being loaded:

  • ClassFormatError (corrupt class files)

  • NoClassDefFoundError (missing class file)

  • UnsatisfiedLinkError (missing library for native definitions)

  • VerifyError (invalid bytecodes)

This last is hard to get by writing in Java; it would indicate a serious compiler error or by writing class files in some other way than Java.

Methods

From a binary compatibility standpoint, a method is made up of four things:

  • The name

  • The return type

  • The arguments

  • Whether or not it's static

If you change any of these, it is a different method as far as the JVM is concerned. Take a look at this class:

class Ticket
{
  boolean isValid() { ... }
}

If you decide to change the Ticket class to accept a Date:

class Ticket
{
  boolean isValid(Date when) { ... }
  
}

then you can't substitute the new class for the old one. Anybody expecting to find the isValid() method will get cranky, and you'll get an error message like this:

java.lang.NoSuchMethodError: Ticket.isValid()Z

(The ()Z is how the JVM represents a method which takes nothing and returns a boolean; we'll discuss it in greater detail in the final installment of this article.)

Personally, I recommend either adding a valid approximation:

  boolean isValid() { return isValid(new Date()); }

or at least providing a meaningful warning that the program has gotten dangerously out of synch.

  boolean isValid() { throw new Error("Program out of synch. 
            Call 1-800-555-CODE to complain."); }

If nobody is actually using isValid, you can feel free to change it. But you can't be sure who's using isValid until you actually run or recompile the other code.

The JVM figures out which method body to call by using a technique called virtual method dispatch. It decides which method body to use based on the exact instance on which the method is called. Think of it as very late binding.

As Java programmer, you're already intimately familiar with virtual method dispatch. Java uses the method body found in the class to which the instance belongs. If a particular class doesn't have a method with exactly that name, arguments, and return type, it inherits one from the super class. (It doesn't inherit the static property, since static things aren't inherited the way virtual methods are.)

Java's binary compatibility rules mean that the inheritance is managed at run time rather than at compile time. Suppose you start with:

class Play
{
  void perform()
  {
	System.out.println("Oklahoma! Where the wind comes sweeping down the plain");
  }
}

class ShakespearePlay extends Play
{
  void perform()
  {
	System.out.println("To be or not to be.");
  }
}

class Hamlet extends ShakespearePlay
{
}

class RichardIII extends ShakespearePlay
{
  void perform()
  {
	System.out.println("Now is the winter of our discontent.");
  }
}
class Othello extends ShakespearePlay
{
  void perform()
  {
	System.out.println("Chaos is come again.");
  }
}

Then

Play play = new Hamlet();
play.perform();

prints

To be or not to be.

That's because the method body for perform is chosen at run time. Although Hamlet doesn't have a method body for perform, it inherits one from ShakespearePlay. It doesn't use the one from the generic Play, because the perform in ShakespearePlay overrides it.

We can change Hamlet dynamically, without recompiling ShakespearePlay, to pick another quote:

class Hamlet extends ShakespearePlay
{
  System.out.println("Get thee to a nunnery");
}

And now:

Play play = new Hamlet();
play.perform();

prints

Get thee to a nunnery

But

Play play = new ShakespearePlay();
play.perform();

still prints

To be or not to be.

You can remove the body of ShakespearePlay:

class ShakespearePlay extends Play
{
}

and now that same code prints:

Oklahoma! Where the wind comes sweeping down the plain.

which is, of course, very wrong. So, perhaps, you should forbid this case by making ShakespearePlay abstract:

abstract class ShakespearePlay extends Play
{
}

Now, if you now run the perform example without recompiling, you'll get:

java.lang.InstantiationError: ShakespearePlay

Because ShakespearePlay is abstract and cannot be instantiated, the JVM detects it at runtime and won't allow the code to run.

Fields

Fields are different from methods. When you remove a method, it's possible for your Java class to inherit a different method with the same name and arguments, and to override parent class methods. Fields can't be overridden, which has an effect on their binary compatibility.

For example, let's look at these three classes:

class Language
{
  String greeting = "Hello";
}

class German extends Language
{
  String greeting = "Guten tag";
}

class French extends Language
{
  String greeting = "Bon jour";
}

The code:

void test1() { System.out.println(new French().greeting); }

prints

Bon jour

but

void test2() { System.out.println(((Language) new French()).greeting); }

prints

Hello

That's because the field selected depends on the class you think you're accessing. In the first case, test1 knows it's accessing a French object, so it prints the French greeting. In the second case, even though it's really accessing a French object, test2 prints the standard (in this case, English) greeting.

You might choose to eliminate the standard greeting:

class Language
{
}

But if you try to run test2 without recompiling, you get:

java.lang.NoSuchFieldError: greeting

That's the JVM's way of detecting the error you'd get if you recompiled test2:

cannot resolve symbol
symbol : variable greeting 
location: class Language
	System.out.println(((Language) new French()).greeting);

The test1 code continues to run just fine, without recompilation, because it doesn't depend on the existence of a greeting in Language.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020