Wrapper methods are written to insulate callers from change, but only where there is clear risk of change.  For example, if twenty developers depended on a web service API that had a history of poor data quality, architects may decide to wrap the API to control risk.  Wrapper classes/methods need a clear purpose to exist.  A wrapper class must add some value, save some time, increase stability.

blog comments powered by Disqus