Marker interface pattern: Difference between revisions

Revision as of 23:13, 2 May 2022

Latest revision as of 13:29, 20 July 2025

(6 intermediate revisions by 5 users not shown)

Line 1:

{{Short description|Design pattern in computer science}}

{{Refimprove|date=June 2013}}

The '''marker interface pattern''' is a [[design pattern (computer science)|design pattern]] in [[computer science]], used with languages that provide run-time type information about objects. It provides a means to associate metadata with a class where the language does not have explicit support for such metadata.

Line 6 ⟶ 7:

| last = Bloch

| first = Joshua

| title = Effective Java (Second edition)

| page = [https://archive.org/details/effectivejava00bloc_0/page/179 179]

| chapter = Item 37: Use marker interfaces to define types

Line 14 ⟶ 15:

| chapter-url-access = registration

| chapter-url = https://archive.org/details/effectivejava00bloc_0/page/179

| edition = Second

}}</ref> (also called '''tagging interface''') which is an empty interface,<ref>{{Cite web |date=2017-03-06 |title=Marker interface in Java |url=https://www.geeksforgeeks.org/marker-interface-java/ |access-date=2022-05-01 |website=GeeksforGeeks |language=en-us}}</ref> and methods that interact with instances of that class test for the existence of the interface. Whereas a typical [[interface (computer science)|interface]] specifies functionality (in the form of method declarations) that an implementing class must support, a marker interface need not do so. The mere presence of such an interface indicates specific behavior on the part of the implementing class. Hybrid interfaces, which both act as markers and specify required methods, are possible but may prove confusing if improperly used.

Line 26 ⟶ 28:

==Critique==

A majorOne problem with marker interfaces is that, since an interface defines a contract for implementing classes, and that contract is inherited by all subclasses., Thisa meansmarker thatcannot you cannotbe "unimplementunimplemented" a marker. In the example given, if you create aany subclass that you do not wantintended tofor serializeserialization (perhaps because it depends on transient state), you must resort to explicitly throwingthrow <code>NotSerializableException</code> exceptions (per <code>ObjectOutputStream</code> docs).

Another solution is for the language to support [[metadata]] directly:

Line 34 ⟶ 36:

==See also==

*[[Design marker]]s for an expansion of this pattern.

== Further reading ==

''Effective Java''<ref>{{Cite book |last=Bloch |first=Joshua |url=https://www.worldcat.org/oclc/1018432176 |title=Effective Java |date=2018 |isbn=978-0-13-468599-1 |edition=Third |___location=Boston |oclc=1018432176}}</ref> by [[Joshua Bloch]].

==References==

{{Reflist}}

== Further reading ==

''Effective Java''<ref>{{Cite book |last=Bloch |first=Joshua |url=https://www.worldcat.org/oclc/1018432176 |title=Effective Java |date=2018 |isbn=978-0-13-468599-1 |edition=Third |___location=Boston |oclc=1018432176}}</ref> by [[Joshua Bloch]].

{{Design Patterns patterns}}