| http://www.w3.org/ns/prov#value | - Now in case there is a whole architectural change in the third party jar, my project also needs to be restructured which is quite a laborious work. what i want is a kind of design where any future changes in the third party jar(like package restructuring or API changes) I am using will have a minimal effect on my code. i have read some design patterns but not very sure which will be what combination
|
