JOPA 0.11.0 has just been released. We are updating version minor since there are some changes in the API. The Query API now supports processing results using Java 8 streams. Some...
JOPA 0.11.0 has just been released. We are updating version minor since there are some changes in the API. The Query API now supports processing results using Java 8 streams. Some bugs/issues have been fixed. In addition, some deprecated constants and classes were finally removed.
JOPA 0.10.8 has just been released. The main added feature of this release is support for plural annotation properties. Besides that, several minor fixes have been fixed.
JOPA 0.10.7 has just been released. We have added support for the Java 8 Date/Time API, so now entities can use, for example,
Instant as mapped entity attribute types.
Besides that, a bug which caused issues with caching instances of classes overriding
equals/hashCode has been fixed.
This is a maintenance release, which fixes several bugs. Also,
VariableResult used by
SparqlResultMapping now supports unbound variables, so that it can be used with OPTIONAL patterns.
The new release of JOPA brings, besides code improvements and fixes also modified exception structure, so that all JOPA exceptions are now subclasses of
In addition, thanks to the newly defined
aop.xml file, load time weaving can be used on projects using JOPA, allowing finally to switch to Java 9/10. More on this on the project wiki.
This release fixes a critical NPX bug caused by inherited indirect collections not being removed when an entity was detached from the persistence context.
The latest release of JOPA fixes an issue in SPARQL query parser, which problems with property paths used together with variables.
In addition, it brings support of setting the in-memory store used by the Jena and RDF4J OntoDriver at runtime. This means that the application is able to set a different in-memory store than the one it was initially connected to. This may be useful when the application sets up a memory store and populates it with some predefined data and then wants to access it from JOPA.
The latest release of JOPA contains several bug fixes and improvements in the Jena driver. The most notable change is the support for reloading file-based storage in OntoDriver. This allows the application to reload data which might have been changed externally.
The reload is supported by the
ReloadableDataSource, which can be unwrapped from an
EntityManagerFactory. The following example shows this:
final EntityManagerFactory emf = // initialization of the Persistence
// Do some stuff
Note that the reloading happens outside any running transactions.
A new release of JOPA is out and it contains a long awaited feature - implementation of the Jena OntoDriver. It allows to access Jena-based storage (e.g. TDB) from JOPA, further extending capabilities of JOPA.
An example project using the Jena driver will be published in https://github.com/kbss-cvut/jopa-examples soon.
This is a maintenance release. It fixes a bug in the clone building process, which caused errors when entities with circular references were encountered.
The next release will introduce a beta version of the Jena OntoDriver, which is currently under development.
- Ontology-Based Data Integration
- Unified Foundational Ontology
- Ontology Engineering
- Spatial and Temporal Ontologies
- Semantic Web
- Semantic Web Stack RDF(S), OWL (2), SPARQL,
- Expressive Queries to Semantic Web Ontologies, SPARQL-DL,
- Annotated Information Search
- Semantic Information Systems
- Enterprise Java,
- OO programming,
- Web & mobile technologies,
- Linked Data & Open Data
- Data Quality
- Semantic Data Description
Our vision of a semantic vocabulary for sharing and discovery of government data assets has been accepted to JWS, see https://ssrn.com/abstract=3303148
JOPA 0.10.7 has just been released. We have added support for the Java 8 Date/Time API, so now entities can use, for example, LocalDate , LocalDateTime , or Instant as mapped entity...