4.8 Java4050: core collection interfaces  (Page 5/5)

Optional Collection operations

The following list shows the optional operations in the Collection interface. Each of these methods has the ability to modifythe contents of the collection.

• add()
• addAll()
• clear()
• remove()
• removeAll()
• retainAll()

Optional Map operations

The following list shows the optional operations in the Map interface. Each of these methods also has the ability to modify the contents ofthe map.

• clear()
• put()
• putAll()
• remove()

Many methods are not optional

In both cases, the interface declares numerous other methods that are not optional. Generally, the non-optional methods don't have the ability tomodify the collection. For example, the get method of the Map interface is not optional. Although the get method receives an incoming key and returns the value to which the key maps, the method doesn't have the ability to modify the contents of the collection.

Run the program

I encourage you to copy the code from Listing 1 and paste it into your Java editor. Thencompile and execute it.

Run the program and observe the results. Experiment with the code. Make changes, run the program again, and observe the results of your changes. Make certain that youcan explain why your changes behave as they do.

Summary

A collections framework contains at least the following items:

• interfaces
• implementations
• algorithms

The Java Collections Framework defines eight core interfaces, in two distinct trees. One tree is rooted in Collection and the other is rooted in Map .

The basic purpose of the core interfaces is to make it possible for collections to be manipulated without regard for how they are implemented, solong as the implementation satisfies the contracts of the interfaces.

When the same method name (and signature) is called on references to collections of different types, the behavior of the method is likely to be different for each collection.However, in each case, that behavior will be appropriate for the type of collection object on which the method is called. This is polymorphicbehavior.

Six of the methods declared in the Collection interface are optional insofar as being supported by implementing classes is concerned. The optional methodsall have the ability to modify the contents of the collection. Those implementing classes that don't support an optional method must throw an UnsupportedOperationException if that method is called on an object of the class. Similarly four of the methods declared in the Map interface are optional.

Many methods declared in the Collection interface are not optional. Generally, the non-optional methods don't have the ability to modify thecollection.

What's next?

In the next module, I will discuss and illustrate some of the details of the core interfaces and the general-purpose implementations in the Java CollectionsFramework. For example, I will discuss the difference between a set and a list . I will also discuss the difference between ordered and sorted . I will discuss the fact that additional stipulations are applied as you progressdown the framework interface hierarchy. In order to help you learn and retain the material, I will provide a couple of short quizzes.

Miscellaneous

This section contains a variety of miscellaneous information.

-end-