On 07/01/15 23:50, Martynas Jusevičius wrote:
I was reading about Java 8 Lambda Expressions and it appeared to me
that they maybe could be used as a sort of functional ORM on Jena:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/Lambda-QuickStart/index.html
Just a thought. Has any
I was reading about Java 8 Lambda Expressions and it appeared to me
that they maybe could be used as a sort of functional ORM on Jena:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/Lambda-QuickStart/index.html
Just a thought. Has anyone looked at how Jena could be improved using l
PA4RDF uses the graph directly for storage. So there is no detachment from
the model. This changes the semantics somewhat.
That being said, PA4RDF only performs locks when it goes to update an
Object (in the SPO sense). Each write is atomic.
I would have to go look at the code but I think that
I have been using Elmo for some years now.
It is the Sesame-equivalent of PA2RDF.
And I think it works really well.
Graph DB maps nicely to an object structure.
One thing I learnt to be careful about, in Elmo:
Entities, once instanciated, are detached from the model.
They do not synchronize automa
PA4RDF works by mapping java methods to values in the graph and returning
those values converted to the proper Java type. It uses the graph data
directly (i.e. it does not make a copy)
so that given a properly annotated interface like:
interface X {
String getName();
void setName(String name
I have find it really nice to use the OntModel and the more specific
types there, like Individual.
It means I have to pre-load an ontology or RDFS schema (from URI or
classpath) and set static fields for the different properties and
classes I will enquire/construct with.
See
https://github.com/t
David,
in my experience this approach only gives you the object-model
impedance mismatch and no real advantages.
Have you considered working directly on Jena Models and Resources?
Martynas
graphityhq.com
On Thu, Nov 20, 2014 at 11:13 PM, David Moss wrote:
> Until now I have been treating Jena
2014-11-20 23:13 GMT+01:00 David Moss :
> Until now I have been treating Jena and RDF like a database connection.
> I retrieved data and immediately converted it to familiar Java objects with
> fields, getters, setters and methods.
>
>
> Recently I have been wondering if it might be better to keep
Thank you for pointing me to this Claude, it is exactly what I was trying to
achieve, but much more elegant.
DM
-Original Message-
From: Claude Warren [mailto:cla...@xenei.com]
Sent: Friday, 21 November 2014 6:04 PM
To: users@jena.apache.org
Subject: Re: Using Model inside Java
If you want a half way step, take a look at PA4RDF (
http://pa4rdf.sourceforge.net/) -- Persistence Annotations for RDF.
This package takes interfaces, abstract classes or concrete classes, and
through the magic of annotations and dynamic proxies overlays them onto a
graph so that a specific node
Until now I have been treating Jena and RDF like a database connection.
I retrieved data and immediately converted it to familiar Java objects with
fields, getters, setters and methods.
Recently I have been wondering if it might be better to keep the data as a
Jena Model within the object and use
11 matches
Mail list logo
