ReBA: a tool for generating binary adapters for evolving java libraries

ABSTRACT

Although in theory the APIs of software libraries and frameworks should be stable, they change in practice. This forces clients of the library API to change as well, making software maintenance expensive. Changing a client might not even be an option if its source code is missing or certain policies forbid its change. By giving a library both the old and the new API, clients can be shielded from API changes and can run with the new version of the library.

This demo presents our tool, ReBA, that automatically generates compatibility layers between new library APIs and old clients. In the first stage, ReBA generates another version of the library, called adapted-library, that supports both the old and the new APIs. In the second stage, ReBA shrinks the adapted-library into a minimal, client-specific compatibility layer containing only classes truly required by the client. Evaluation on controlled experiments and case studies using Eclipse core libraries shows that our approach effectively adapts clients to new library versions, and is efficient.

REFERENCES

• 1: Ittai Balaban , Frank Tip , Robert Fuhrer, Refactoring support for class library migration, Proceedings of the 20th annual ACM SIGPLAN conference on Object oriented programming, systems, languages, and applications, October 16-20, 2005, San Diego, CA, USA
• 2: Kingsum Chow , David Notkin, Semi-automatic update of applications in response to library changes, Proceedings of the 1996 International Conference on Software Maintenance, p.359, November 04-08, 1996
• 3: Danny Dig , Ralph Johnson, How do APIs evolve? A story of refactoring: Research Articles, Journal of Software Maintenance and Evolution: Research and Practice, v.18 n.2, p.83-107, March 2006 [doi>10.1002/smr.v18:2]
• 4: Danny Dig , Stas Negara , Vibhu Mohindra , Ralph Johnson, ReBA: refactoring-aware binary adaptation of evolving libraries, Proceedings of the 30th international conference on Software engineering, May 10-18, 2008, Leipzig, Germany [doi>10.1145/1368088.1368148]
• 5: Eclipse Foundation. http://eclipse.org.
• 6: Refactoring: improving the design of existing code, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 7: Johannes Henkel , Amer Diwan, CatchUp!: capturing and replaying refactorings to support API evolution, Proceedings of the 27th international conference on Software engineering, May 15-21, 2005, St. Louis, MO, USA [doi>10.1145/1062455.1062512]
• 8: Ralph Keller , Urs Hölzle, Binary Component Adaptation, Proceedings of the 12th European Conference on Object-Oriented Programming, p.307-329, July 20-24, 1998
• 9: S. Roock and A. Havenstein. Refactoring tags for automatic refactoring of framework dependent applications. In XP?02, pages 182--185.
• 10: WALA Static Analysis Library. http://wala.sourceforge.net/.
• 11: Alessandro Warth , Milan Stanojević , Todd Millstein, Statically scoped object adaptation with expanders, Proceedings of the 21st annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications, October 22-26, 2006, Portland, Oregon, USA

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.13 Reusable Software

General Terms:
Design, Management

Keywords:
api compatibility, component reuse, libraries, refactoring