Releases: Wolfgang-Schuetzelhofer/jcypher
4.2.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
- Set the planner strategy globally or individually on a per query basis.
- Support for Neo4J 3.4.1
- Fix for minHops(0)
- Collections in the Query API are aware of their component type. This allows expressions like: WHERE.valueOf(path.relations().last().type()).EQUALS("Some_Type") or: WHERE.has(path.nodes().head().label("Some_Label"))
- Fixed Issue with labels retrieval when using AbstractEmbeddedDBAccess and forcing PlannerStrategy.COST.
- Support for Neo4j 3.5.x
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
4.1.1
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
- Set the planner strategy globally or individually on a per query basis.
- Support for Neo4J 3.4.1
- Fix for minHops(0)
- Collections in the Query API are aware of their component type. This allows expressions like: WHERE.valueOf(path.relations().last().type()).EQUALS("Some_Type") or: WHERE.has(path.nodes().head().label("Some_Label"))
- Fixed Issue with labels retrieval when using AbstractEmbeddedDBAccess and forcing PlannerStrategy.COST.
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
4.1.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
- Set the planner strategy globally or individually on a per query basis.
- Support for Neo4J 3.4.1
- Fix for minHops(0)
- Collections in the Query API are aware of their component type. This allows expressions like: WHERE.valueOf(path.relations().last().type()).EQUALS("Some_Type") or: WHERE.has(path.nodes().head().label("Some_Label"))
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
4.0.1
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
- Set the planner strategy globally or individually on a per query basis.
- Support for Neo4J 3.4.1
- Fix for minHops(0)
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
4.0.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
- Set the planner strategy globally or individually on a per query basis.
- Support for Neo4J 3.4.1
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
3.9.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for Neo4J 3.1.1
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Support for Neo4J 3.2.2
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
- Support for Neo4J 3.3.1
- Set the planner strategy globally or individually on a per query basis.
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
3.8.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
- Support for Neo4J 3.1.1
- Support for extended Authentication according to Neo4J's Bolt Driver specification.
- Support for Neo4J 3.2.2
- Registration of shutdown hooks on IDBAccess instances is made optional.
- Public constructors for IDBAccess implementations allow more flexible configurations.
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
3.6.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
- Some improvements like simple construction of literal lists.
- Code compatibility with Java 1.7 (JCypher since 3.5.0 however is built for Java 1.8. This is required, so that JCypher- embedded and- in-memory db access works with Neo4J 3.0.x and upward).
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
3.5.0
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
- Support for Neo4J 3.0.X and the BOLT protocol.
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.
3.4.1
Features:
- Access to Neo4j databases
You can access Neo4j databases in a uniform way, no matter if you access a remote database, an embedded database, or an in-memory database, the only difference is in the initialization part - Query-DSL: Fluent API to formulate JCypher expressions in order to query a Neo4J database;
- A Generic Graph Model which is easily navigable and modifyable.
- Mapping of complex business domains to domain graphs
- Domain Queries Part 1 - Predicate Expressions
Domain Queries provide the power and expressiveness of queries on a graph database, while being formulated on domain objects or on types of domain objects respectively. - Domain Queries Part 2 - Traversal Expressions.
- Domain Queries Part 3 - Collection Expressions (SELECT, REJECT, COLLECT, UNION, INTERSECTION).
- Improved support for multiple domains in a single database.
- Domain Query Concatenation.
- Basic authentication and authorization.
- Transaction API.
- Generic Domain Model.
- Concurrency support for multi client access to the graph database - optimistic locking.
- Concurrency support - thread-safe invocation of 'IDomainAccess' an domain queries.
- JSON Facade in preparation to access JCypher features from other, possibly remote, systems.
- Store domain queries with the domain.
- Use parameters with Query DSL Expressions.
Note: JCypher releases are deployed on Maven Central. You can download binaries and other artifacts from there.
Note: You need the javax.json-api, as well as an implementation e.g. from project glassfish on your classpath. One possible download source: http://www.java2s.com/Code/Jar/j/Downloadjavaxjson10jar.htm.
To access remote databases, you furthermore need a REST client API implementation, e.g. 'Jersey' from project glassfish, on your classpath.
To access embedded and in-memory databases, you need the appropriate Neo4j '.jar' files on your classpath.
(You can find all required dependencies listed in the pom.xml of the jcypher project.