The Jakarta Data specification provides an API for easier data access to various database types, such as relational and NoSQL. A Java developer can access those repositories in several ways, including composing custom query methods on a Repository interface.
Jakarta Data’s goal is to provide a familiar and consistent, Jakarta-based programming model for data access while still retaining the particular traits and strengths of the underlying data store.
A repository abstraction designed to significantly reduce the boilerplate code required to implement data access layers for various types of persistent stores.
@Repository
public interface CarRepository extends CrudRepository<Car, Long> {
List<Car> findByType(CarType type);
Optional<Car> findByName(String name);
}@Inject
CarRepository repository;
...
Car ferrari = Car.id(10L).name("Ferrari").type(CarType.SPORT);
repository.save(ferrari);This project has a testing guideline that will help you understand Jakarta Data’s testing practices. Please take a look at the TESTING-GUIDELINE file.
This project is governed by the Eclipse Foundation Community Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to [email protected].
Having trouble with Jakarta Data? We’d love to help!
Report Jakarta Data bugs at https://github.com/jakartaee/data/issues.
You don’t need to build from source to use the project, but you can do so with Maven and Java 17 or higher.
mvn clean install