se.oyabun.criters.test:criters-test-eclipselink

Criters engine is a framework for automating searches using JPA.

License

License

Categories

Categories

CLI User Interface EclipseLink Data ORM
GroupId

GroupId

se.oyabun.criters.test
ArtifactId

ArtifactId

criters-test-eclipselink
Last Version

Last Version

1.0.1
Release Date

Release Date

Type

Type

jar
Description

Description

Criters engine is a framework for automating searches using JPA.
Project Organization

Project Organization

Oyabun AB

Download criters-test-eclipselink

How to add to project

<!-- https://jarcasting.com/artifacts/se.oyabun.criters.test/criters-test-eclipselink/ -->
<dependency>
    <groupId>se.oyabun.criters.test</groupId>
    <artifactId>criters-test-eclipselink</artifactId>
    <version>1.0.1</version>
</dependency>
// https://jarcasting.com/artifacts/se.oyabun.criters.test/criters-test-eclipselink/
implementation 'se.oyabun.criters.test:criters-test-eclipselink:1.0.1'
// https://jarcasting.com/artifacts/se.oyabun.criters.test/criters-test-eclipselink/
implementation ("se.oyabun.criters.test:criters-test-eclipselink:1.0.1")
'se.oyabun.criters.test:criters-test-eclipselink:jar:1.0.1'
<dependency org="se.oyabun.criters.test" name="criters-test-eclipselink" rev="1.0.1">
  <artifact name="criters-test-eclipselink" type="jar" />
</dependency>
@Grapes(
@Grab(group='se.oyabun.criters.test', module='criters-test-eclipselink', version='1.0.1')
)
libraryDependencies += "se.oyabun.criters.test" % "criters-test-eclipselink" % "1.0.1"
[se.oyabun.criters.test/criters-test-eclipselink "1.0.1"]

Dependencies

compile (3)

Group / Artifact Type Version
se.oyabun.criters : criters-engine jar 1.0.1
org.eclipse.persistence : eclipselink jar 2.5.2
org.slf4j : slf4j-api jar 1.7.21

test (2)

Group / Artifact Type Version
ch.qos.logback : logback-classic jar 1.1.7
se.oyabun.criters.test : criters-test-core-jpa jar 1.0.1

Project Modules

There are no modules declared in this project.
---------------------------------------------------------------------------------------------------
     .aMMMb  dMMMMb  dMP dMMMMMMP dMMMMMP dMMMMb  .dMMMb
    dMP"VMP dMP.dMP amr    dMP   dMP     dMP.dMP dMP" VP
   dMP     dMMMM.  dMP    dMP   dMMMP   dMMMMK   VMMMb
  dMP.aMP dMP AMF dMP    dMP   dMP     dMP AMF dP .dMP
  VMMMP" dMP dMP dMP    dMP   dMMMMMP dMP dMP  VMMMP"
--------------------------------------------------------------------------------------------------- 

Criters Criteria Automation Engine Build Status Maven Central

Configuration

Search filter configuration

<dependency>
    <groupId>se.oyabun.criters</groupId>
    <artifactId>criters-annotation</artifactId>
    <version>${criters-annotation.version}</version>
</dependency>

Annotate your filter objects with the criters filter annotations.

    //
    // Make your object extend Filter<?> for the type of entity you want to find. 
    //
    public class FooFilter extends Filter<Foo> {
        //
        // Use direct parameter restrictions on the entity
        //
        @Parameter(name ="value",
                   restriction = Restriction.EQUALS)
        public Integer getValue() { return 0; }
        //
        // or via a relational property restriction
        //
        @Relations({
            @Relation(name="bars",
                      iterable = true,
                      parameters = {
                @Parameter(name = "id",
                           restriction = Restriction.EQUALS)
            })
        })
        public long getBarId() { return 0L; }
    }

Engine configuration

<dependency>
    <groupId>se.oyabun.criters</groupId>
    <artifactId>criters-engine</artifactId>
    <version>${criters-engine.version}</version>
</dependency>

Use the convenient Criters factory builder to instantiate your criters factory. You then need to configure the factory to use an entity manager or a root, criteria query and criteria builder.

    //
    // Either configure an entity manager
    //
    Criters.<Foo, Filter<Foo>> factory().use(entityManager);
    //
    // or with the root, criteria query and criteria builder directly
    //
    Criters.<Foo, Filter<Foo>> factory().use(root, criteriaQuery, criteriaBuilder);

Spring Data JPA

<dependency>
    <groupId>se.oyabun.criters</groupId>
    <artifactId>criters-spring-data-jpa</artifactId>
    <version>${criters-engine.version}</version>
</dependency>

Annotate your filter object the regular way and let your specifications extend CritersSpecification<E, F extends Filter<E>>.

   public class FooSpecification
           extends CritersSpecification<Foo, Filter<Foo>> {
   
       public FooSpecification(final Filter<Foo> searchFilter) {
   
           super(searchFilter);
   
       }
   
   }

Project Structure

╔═════════════════════════╗ 
║ Criters Project Reactor ║
╚═╤═══════════════════════╝ 
  │   ╔═════════════════════╗
  ├───╢ Criters Annotations ║
  │   ╚═════════════════════╝
  │   ╔════════════════╗
  ├───╢ Criters Engine ║
  │   ╚════════════════╝
  │   ╔═════════════════════════╗
  ├───╢ Criters Spring Data JPA ║
  │   ╚═════════════════════════╝
  │   ╔════════════════════════╗
  ├───╢ Criters Hibernate Test ║
  │   ╚════════════════════════╝
  │   ╔══════════════════════════╗
  ├───╢ Criters EclipseLink Test ║
  │   ╚══════════════════════════╝
  │   ╔═══════════════════════╗
  ├───╢ Criters Core JPA Test ║
  │   ╚═══════════════════════╝
  │   ╔═══════════════════╗
  └───╢ Criters Core Test ║
      ╚═══════════════════╝
se.oyabun.criters.test

Oyabun AB

Open source repositories

Versions

Version
1.0.1
1.0.0