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

Persistence isolation #247

Open
froque opened this issue Jan 11, 2022 · 0 comments
Open

Persistence isolation #247

froque opened this issue Jan 11, 2022 · 0 comments

Comments

@froque
Copy link
Member

froque commented Jan 11, 2022

Persistence isolation

Prototype of the needed changes to isolate Persistence specific entities from the business logic.

Proposed structure

billy
└──billy-core
│    Address
│    AddressEntity
└──billy-core-jpa
│    module to be deleted
│      * This removes duplication but the need to have a "duplicate" for each country creates a false sensation that the base can be used by it self
│      * Other reasons...
│    JPAAddressEntity
└──billy-portugal
│    PTAddress
│    PTAddressEntity
│    PTAddressBuilder
│    PTAddressDAO
└──billy-portugal-jpa
│    JPAPTAddressEntity
│    JPAPTAddressDAOImpl
└──(billy-portugal-ebean)
       * To be added in the future if needed
     EBPTAddressEntity
     EBPTAddressDAOImpl

History

Billy uses JPA API, but relies heavily on Hibernate and was never tested with any other JPA implementation. There was an effort to also use Ebean (#22), but failed and was removed (#226).

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