com.stormpath.sdk.challenge.sms.SmsChallengeCriteria Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of stormpath-sdk-api Show documentation

The Stormpath Java SDK API .jar provides a Java API that your code can use to make calls to the Stormpath API. This .jar is the only compile-time dependency within the Stormpath SDK project that your code should depend on. Implementations of this API (implementation .jars) should be runtime dependencies only.

The newest version!

/*
 * Copyright 2016 Stormpath, Inc.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package com.stormpath.sdk.challenge.sms;

import com.stormpath.sdk.challenge.ChallengeCriteria;
import com.stormpath.sdk.challenge.ChallengeOptions;
import com.stormpath.sdk.query.Criteria;

/**
 * A {@link SmsChallenge}-specific {@link Criteria} class, enabling a SmsChallenge-specific
 * fluentquery DSL. SmsFactorCriteria instances can be
 * constructed by using the {@link SmsChallenges} utility class, for example:
 *  * Challenges.SMS.where(Challenges.SMS.status().eq(SmsChallengeStatus.SUCCESS))
 *     .orderByType()
 *     .limitTo(10));
 * 
 * Sort Order
 * 
 * All of the {@code orderBy*} methods append an {@code orderBy} clause to the query, ensuring the query results reflect
 * a particular sort order.
 * 

 * The default sort order is always {@code ascending}, but can be changed to {@code descending} by calling the
 * {@link #descending()} method immediately after the {@code orderBy} method call.  For example:
 * 
 * ...criteria.orderType().descending()...
 * 
 * Multiple Order Statements
 * You may specify multiple {@code orderBy} clauses and the query results will ordered, reflecting {@code orderBy}
 * statements in the order they are declared.  For example, to order the results first by name (ascending)
 * and then further by status (descending), you would chain {@code orderBy} statements:
 *  * ...criteria
 *     .orderType()
 *     .orderByStatus().descending()
 *     ...
 * 
 *
 * @since 1.1.0
 */
public interface SmsChallengeCriteria extends ChallengeCriteria, ChallengeOptions {
    /**
     * Ensures that the query results are ordered by group {@link SmsChallenge#getMessage()} message}.
     * 
     * Please see the {@link ChallengeCriteria class-level documentation} for controlling sort order (ascending or
     * descending) and chaining multiple {@code orderBy} clauses.
     *
     * @return this instance for method chaining
     */
    ChallengeCriteria orderByMessage();
}