Closed hohwille closed 5 years ago
@vapadwal could you try to solve this on a fork/feature-branch. If all works out, please provide PR. Otherwise lets discuss problems or consider this for https://github.com/devonfw/devcon/issues/135
So we now have 3 different PRs as implementation for this issue:
Community voted for PR #675 which is now merged, hence closing this issue.
oasp4j-jpa
shall provide legacy support and compatibility for previous usage scenarios and projects on top ofoasp4j-jpa-dao
. However, at the moment a refactoring of existing code is required to useLegacyDaoQuerySupport
as a kind of shim to retain old functionality.It would be great if
oasp4j-jpa
could still contain the DAO classes in the same package namespace but extend from classes inoasp4j-jpa-dao
that therefore have to use a new namepsace (different name and/or package). Then the DAO classes could provide the removed methods directly and would retain full API compatibility.