Hi Prabhat,
in general an adapter is just a design
pattern (I guess you're talking about these adapters). So in fact it's not only related to Java.
Usually an adapter is used like a real adapter for a
water hose or something like that. That means you have some kind of class/interface/method signature you want to connect to with another class/interface/method but the interface of the client doesn't fit exactly to that of the service side (for example wrong type, method signature or something like that). Then you can create an adapter which translates between both interfaces so that you don't have do modify neither existing one.
Your example with partially implemented interface methods is a typical use case for adapters too. Swing or AWT make quite some use of it in order to provide convenient implementations (which often do simply nothing) for common interfaces. This way you can extend this class and only override the methods of the implemented interface as needed. Of course this only works if the interface does not require a useful implementation for all methods. You can just search the AWT or Swing API documentation for examples like the MouseAdapter class and many more adapters.
Btw. this is not related to Spring although Spring may make use of this pattern! Please choose the right forum more carefully if you expect to get an answer to you questions quickly
Marco