Releases: kbss-cvut/jopa
Releases · kbss-cvut/jopa
2.1.0
2.0.5
2.0.4
2.0.3
2.0.2
- Fix a NPX when calling
EntityManager.isInferred
with lazy loading proxy (Bug #252). - Allow using multiple values for a query parameter that is written into SPARQL
VALUES
clause (Bug #246). - Dependency updates: RDF4J 5.0.0.
- Update note: Still compatible with server 4 and, with the right configuration,
also 3. However, if you are passing repository configuration file to JOPA, make sure it uses the new configuration vocabulary.
- Update note: Still compatible with server 4 and, with the right configuration,
2.0.1
- Proper implementation of
EntityManager.getReference
after 2.0.0 rewrite (Enhancement #233). - Log JOPA version and build date on persistence unit startup (Enhancement #243).
- Prevent
AssertionError
onEntityManager.flush
calls (Bug #240). - Fix incorrect SOQL to SPARQL translation when traversing reference and using identifier (Bug #234).
- Fix issues with interaction of lazy loading with cascading (Bug #248).
- Dependency updates: RDF4J 4.3.12.
2.0.0
This is a big release containing potentially breaking changes.
In summary: AspectJ is no longer needed to build projects using JOPA. Java 17 is the minimum required Java version.
Changes:
- Rewrote change tracking and lazy loading to not require AspectJ and use generated proxy classes and change calculation on commit (Enhancement #145, #231). See the wiki for details. This should significantly simplify adoption of JOPA in projects.
- Added support for RDF collections (Enhancement #51).
(Potentially) Breaking changes:
- Modified generation of classes and constants in OWL2Java, using ontology prefixes to disambiguate terms with the same label (Enhancement #85).
- Internal APIs were moved from
jopa-api
tojopa-impl
, so that they can be changed without bumping version major (Enhancement #146). - Java 17 is now minimum Java version (Task #147).
- Updated to Jena 5.0.0, RDF4J 4.3.11.
- Removals of deprecated APIs.
EntityManager
andEntityManagerFactory
are nowAutoCloseable
(in alignment with JPA).