Marker interface pattern: Difference between revisions

Content deleted Content added
m Fix links for renamed page
reorder sections; +cat Category:Java programming language
Line 8:
 
Still, this is generally a good idea, as subclasses usually ''do'' inherit behaviors from their parents and should inherit the marker interfaces as well.
 
== Critique ==
The implementation of this pattern presented above is rather specific to Java. Other object models support rich ways of quickly querying static data. For example, [[.NET Framework|.NET]] supports attributes that can be used to associate any type of data with a class or with its members. As of [[J2SE]] 5.0, Java supports [[reflection (computer science)|reflective]] [[annotation]]s that can be used to associate attributes with classes, interfaces, methods, [[Constructor (computer science)|constructors]], [[Field (computer science)|fields]] and [[Java package]]s. Annotation allow a rich and fine-grained association of [[metadata]] to program elements.
 
== See also ==
* [[Design Markers]] for an expansion of this pattern.
 
==Critique==
The implementation of this pattern presented above is rather specific to Java. Other object models support rich ways of quickly querying static data. For example, [[.NET Framework|.NET]] supports attributes that can be used to associate any type of data with a class or with its members. As of [[J2SE]] 5.0, Java supports [[reflection (computer science)|reflective]] [[annotation]]s that can be used to associate attributes with classes, interfaces, methods, [[Constructor (computer science)|constructors]], [[Field (computer science)|fields]] and [[Java package]]s. Annotation allow a rich and fine-grained association of [[metadata]] to program elements.
 
[[Category:Software design patterns]]
[[Category:Java programming language]]