All Classes and Interfaces

Class
Description
Provides a base superclass for entities which should have auditable capabilities, providing
 
Provides a base superclass for entities which should have auditable capabilities, providing
 
 
 
Our standard CreateService which uses a repository that uses Long id's
A convenience CRUD service, which combines the essential CRUD services
Delete by api id is a composed service, it exists of services that provide: - findByApiId - deleteById It's composed to use the same implementation, which re-uses code that also handles OnDeleteEvents
Our standard delete service which uses a repository that uses Long id's
A convenience full service, which can be used to include all the standard services that we have
A convenience full service, which can be used to include all the standard services that we have
Provides a default implementation for the create service
Provides a default implementation for the delete service
 
 
Provides a default implementation of the findAll service
 
Provides a generic implementation of the find by ids
 
Provides a default implementation of the findAll service
Defines a default implementation of update
This interfaces specifies that we return the default
This interfaces specifies that we return the default
 
A more specific default repository that includes looking up entities by API id
 
 
A repository with standard JpaRepository JpaSpecificationExecutor support and Long id usage.
Bxd specific Jpa implementation of OnCreateListener
Bxd specific Jpa implementation of OnDeleteListener
Bxd specific Jpa implementation of OnUpdateListener
QAbstractApiBaseEntity is a Querydsl query type for AbstractApiBaseEntity
QAbstractBaseEntity is a Querydsl query type for AbstractBaseEntity
 
 
Our standard find all service which uses a repository that uses Long id's
Our standard find by api id service which uses an API repository, which has an extra findByApiId Because the most generic services facilitate no support for finding an entity by anything else than it's own id, we need to implement it here to make it part of our more specific Jpa service implementation
Our standard find by api ids service which uses an API repository, which has an extra findByApiIds Because the most generic services facilitate no support for finding an entity by anything else than it's own id, we need to implement it here to make it part of our more specific Jpa service implementation
Our standard find by id's service which uses a repository that uses Long id's
Our standard find by id's service which uses a repository that uses Long id's
 
 
Our standard find all service which uses a repository that uses Long id's
Our standard update service which uses which uses a repository that uses Long id's