Example usage for org.springframework.data.jpa.domain Specification interface-usage

Introduction

In this page you can find the example usage for org.springframework.data.jpa.domain Specification interface-usage.

Usage

From source file com.globalhackv.app.repository.CitationSpec.java

public class CitationSpec implements Specification<Citation> {

    private final Citation example;

    public CitationSpec(Citation example) {
        this.example = example;

From source file org.lightadmin.api.config.utils.DomainTypeSpecification.java

public interface DomainTypeSpecification<T> extends Specification<T>, Serializable {

}

From source file net.kaczmarzyk.spring.data.jpa.domain.PathSpecification.java

/**
 * @author Tomasz Kaczmarzyk
 */
public abstract class PathSpecification<T> implements Specification<T> {

    protected String path;

From source file org.zlogic.vogon.web.data.TransactionFilterSpecification.java

/**
 * Spring JPA Repository specification for filtering of transactions
 *
 * @author Dmitry Zolotukhin [zlogic@gmail.com]
 */
public class TransactionFilterSpecification implements Specification<FinanceTransaction> {

From source file com.github.lothar.security.acl.jpa.spec.DenyAllSpecification.java

public class DenyAllSpecification<T> implements Specification<T> {

    @Override
    public Predicate toPredicate(Root<T> root, CriteriaQuery<?> query, CriteriaBuilder cb) {
        return cb.disjunction();
    }

From source file net.kaczmarzyk.spring.data.jpa.domain.JoinFetch.java

/**
 * <p>Extension to specification-arg-resolver to allow fetching collections in a specification query</p>
 *
 * @author Tomasz Kaczmarzyk
 * @author Gerald Humphries
 */

From source file net.kaczmarzyk.spring.data.jpa.domain.EmptyResultOnTypeMismatch.java

/**
 * <p>Wrapper that turns a {@code Specification} into a one that always produces in an empty result
 * (i.e. {@code where 0 = 1}) in case of a type mismatch (e.g. when type on path is {@code Long}
 *  and the value from the HTTP parameter is not a numeric.</p>
 * 
 * <p> It's useful for polymorphic "OR" queries such as {@code where id = ? or name = ?}.

From source file com.github.lothar.security.acl.jpa.spec.BiFunctionSpecification.java

public class BiFunctionSpecification<T> implements Specification<T> {

    private BiFunction<Root<T>, CriteriaBuilder, Predicate> predicateFunction;

    public BiFunctionSpecification(BiFunction<Root<T>, CriteriaBuilder, Predicate> predicateFunction) {
        this.predicateFunction = predicateFunction;

From source file com.github.lothar.security.acl.jpa.spec.AllowAllSpecification.java

public class AllowAllSpecification<T> extends NamedBean implements Specification<T> {

    @Override
    public Predicate toPredicate(Root<T> root, CriteriaQuery<?> query, CriteriaBuilder cb) {
        return cb.conjunction();
    }

From source file net.kaczmarzyk.spring.data.jpa.domain.Conjunction.java

/**
 * Helper for easier joining lists of specs with {@code AND} operator
 * 
 * @author Tomasz Kaczmarzyk
 */
public class Conjunction<T> implements Specification<T> {

• «
• 1
• 2
• »