Prasanna Lakshmi Tallapaka wrote:
Many thanks for your reply. This was implicit and is going on. But not of much help.
Can you explain to us why it didn't help? We can't elaborate on your issue if we don't know why.
And explaining what is a marker interface... etc. when the google links does a good job is just a bit silly.
As for the "business requirement" part of your question, that doesn't really make sense. The "marker interface" is a technique (or pattern, for those who like that terminology). It may be used indirectly to solve a "business requirement", but otherwise, is unrelated.
Thanks for your responses. I am aware of what a marker interface is. But was not aware as which business requirement would drive a technologist to implement it. Otherwise, even it is fine to think that it is just used for the purpose. Eg : java.io.Serializable is a marker interface implementing which serializes an object. Similarly, java.lang.Cloneable. Thought if I could know some more to store in my KB and share with needy.
I would be glad to know the marker interfaces in standard JDK.
There is an essentially infinite number of ways a marker interface could be used (although these days annotations are probably the preferred choice--marker interfaces were always a bit suspect to me). They're used any time there's a need to indicate or implement capabilities or possibilities outside of a strict class hierarchy.
I think in business it is used because it is easy to understand which class object is going to be serialzed although for that they don't have to implement any method of it, but it is easy understanding for the coder so the mistakes can be avoided.........
@kaustubh: You're referring to Serializable, I assume. It's not just to "avoid mistakes", it's to tell the JDK that the object may be serialized. And you do need to provide a serialVersionUID even though no methods need to be implemented.