AdaptorGen Home

How often do you face the dilemma of isolating your code from any external libraries you may be using?
It could be a real library, or the auto generated proxies generated by a service reference to an external web service.
Either way, the API you get is not at your control and may change at any time in the future.
You know that "by the book" you should do something with it, but is it worth all the work? Will it ever change? Would the change be easy to digest if you reference the API directly?
So you have two options:
1 - Use the library as is in your business classes and be ready to adjust them if the library changes.
2 - Create a boundary facade to isolate the external library and keep maintaining it.

This tool aims at giving you a third option:
Auto generate Isolation classes around the library, initially with identical interface, and keep the option to override whatever you need in the future.
When the external library does change, you can decide if you want to reflect the new version API to your application classes, or keep the old API (and override the adapters).

How it works:
External Library -> Generate Adaptors -> Use Adaptors instead of external lib classes -> Override Adaptors as needed, keeping your application isolated.

See:
[How to get the source code]
[How to generate adaptors]
[How to override generates adaptors]

---

Project Members:

• Michael Angel (admin)

The wiki uses Markdown syntax.