About Jakarta Data Applications
Jakarta Data provides a repository programming model for data access. You declare a repository interface, and WebLogic Server supplies its implementation during deployment. A CDI-managed component can inject the repository.
WebLogic Server supports Jakarta Data 1.0 with Jakarta Persistence. See the Jakarta Data Specification.
The optional Jakarta NoSQL integration uses server-supplied Eclipse JNoSQL and supports several NoSQL providers in DOCUMENT mode.
Choose a Persistence Model
Choose the entity model before declaring the repository. The following table compares the two paths.
| Topic | Jakarta Persistence | Jakarta NoSQL |
|---|---|---|
| Root mapping | jakarta.persistence.Entity |
jakarta.nosql.Entity |
| Embedded mapping | Jakarta Persistence mapping rules | Supported jakarta.nosql.Embeddable mappings |
| Data store | Visible persistence unit | Local alias bound to a global NoSQL resource |
| Transaction integration | Applicable JTA participation | No participation in JTA global transactions |
| Configuration | Persistence-unit configuration | Administrator-managed descriptor and deployer-approved binding |
Selecting a provider does not convert an entity between mapping models. A class with both annotation families does not create a shared persistence context or identical mapping semantics.
Prepare the Application
WebLogic Server supplies the Eclipse JNoSQL mapping components and provider modules, together with the Oracle NoSQL client libraries. Applications do not need to package these JARs.
For MongoDB, Amazon DynamoDB, Couchbase, Apache CouchDB, Elasticsearch, and Apache Solr, you must supply the selected provider’s client JARs and any additional runtime dependencies required by its JNoSQL provider. Add these libraries to the server startup classpath on every server hosting the NoSQL resource. Use library versions compatible with the JNoSQL version supplied by WebLogic Server.
Repository discovery covers supported WAR and EJB modules, including modules in an EAR. Make repositories, entities, and embedded types visible within the owning deployment’s supported discovery and class-loading scope.
Application-provided JNoSQL mapping settings and MicroProfile configuration do not configure WebLogic-managed NoSQL resources.