Home/ Questions/Q 6646755
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T00:27:20+00:00

I have the following scenario: I am using a very big external library in

  • 0

I have the following scenario: I am using a very big external library in my Eclipse RCP application for a specific purpose.

At this point in time I am not sure if I may not have to replace this library in the future to another one (because it does not provide the necessary functionality or something like that). Also I have users using this library from day one so I would like to encapsulate the library, giving me at least a chance of changing the library in the future without the user noticing or having to change anything in their code.

Is there a simple way to encapsulate a whole library in some automated fashion?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Unless the part of the library’s interface you are actually using is completely trivial, or standardized the way JSF or JAX-B are (in which case you don’t need encapsulation) this is a completely wasted effort.

    I can guarantee that if you have to switch to a different library, the encapsulation would prove worthless because the other library has different underlying concepts and usage patters that cannot be made to fit the existing ones.

    • 0