Marker interface pattern
This article needs additional citations for verification. (June 2013) |
The marker interface pattern is a
To use this pattern, a
Example
An example of the application of marker interfaces from the Java programming language is the Serializable
interface:
package java.io;
public interface Serializable {
}
A class implements this interface to indicate that its non-transient data members can be written to an ObjectOutputStream
. The ObjectOutputStream
private method writeObject0(Object,boolean)
contains a series of instanceof
tests to determine writeability, one of which looks for the Serializable
interface. If any of these tests fails, the method throws a NotSerializableException
.
Critique
A major problem with marker interfaces is that an interface defines a contract for implementing classes, and that contract is inherited by all subclasses. This means that you cannot "unimplement" a marker. In the example given, if you create a subclass that you do not want to serialize (perhaps because it depends on transient state), you must resort to explicitly throwing NotSerializableException
(per ObjectOutputStream
docs)
Another solution is for the language to support metadata directly:
- Both the reflection.
- In Python, the term "marker interface" is common in Zope and Plone. Interfaces are declared as metadata and subclasses can use
implementsOnly
to declare they do not implement everything from their super classes.
See also
- Design markers for an expansion of this pattern.
References
- ^
Bloch, Joshua (2008). "Item 37: Use marker interfaces to define types". Effective Java (Second ed.). Addison-Wesley. p. 179. ISBN 978-0-321-35668-0.
- ^ "Marker interface in Java". GeeksforGeeks. 2017-03-06. Retrieved 2022-05-01.
Further reading
Effective Java[1] by Joshua Bloch.
- OCLC 1018432176.)
{{cite book}}
: CS1 maint: location missing publisher (link