Skip to content

Persistence isolation #247

@froque

Description

@froque

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).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions