Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide abstact interface for hawkBits repository implementation #100

Closed
9 tasks done
kaizimmerm opened this issue Mar 21, 2016 · 1 comment
Closed
9 tasks done
Milestone

Comments

@kaizimmerm
Copy link
Contributor

kaizimmerm commented Mar 21, 2016

Currently hawkBits interfaces interact directly with the repository implementation. That makes it very hard to evaluate/implement alternative implementations on different persistence providers (e.g. MongoDB, Geode, Cassandra etc.).

What we should do:

  • Provide interfaces for the repository services.
  • Migrate current repository to be a JPA implementation.

Tasks:

  • Split management methods (interface and JPA impl)
  • Split model POJOs (interface and JPA imply)
  • Remove org.springframework.data.jpa.domain.Specification from API
  • Split maven modules into API and JPA
  • Refactor TestDataUtils to use new API.
  • Refactor default data generation to use new API and create more reasonable type setup.
  • Document new setup in wiki.
  • Remove dependencies on JPA part from the other modules (especially the tests) and use new API instead
  • Provide auto configuration for implementations
kaizimmerm added a commit to bosch-io/hawkbit that referenced this issue May 13, 2016
… services into API

and Jpa implementation.

Signed-off-by: Kai Zimmermann <[email protected]>
@kaizimmerm
Copy link
Contributor Author

Moved the interface refactoring part to #197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant