public class Schema extends Object
A schema could have two states:
NoSyncValidationException
To check the schema state you can use method . Note that invoking validateAsync(java.lang.Object)
generally doesn't have any additional overhead than invoking validateSync(java.lang.Object)
.
The schema can mutate the state in time, e.g. if you have a schema that is asynchronous because of a $ref
,
after the first validation the external schema is cached inside SchemaRouter
and this schema will switch to synchronous state
original
non RX-ified interface using Vert.x codegen.Modifier and Type | Field and Description |
---|---|
static io.vertx.lang.rx.TypeArg<Schema> |
__TYPE_ARG |
Constructor and Description |
---|
Schema(Object delegate) |
Schema(Schema delegate) |
Modifier and Type | Method and Description |
---|---|
boolean |
equals(Object o) |
Schema |
getDelegate() |
Object |
getJson() |
JsonPointer |
getScope() |
int |
hashCode() |
boolean |
isSync() |
static Schema |
newInstance(Schema arg) |
String |
toString() |
Future<Void> |
validateAsync(Object json)
Validate the json performing an asynchronous validation.
|
void |
validateSync(Object json)
Validate the json performing a synchronous validation.
|
public static final io.vertx.lang.rx.TypeArg<Schema> __TYPE_ARG
public Schema getDelegate()
public Future<Void> validateAsync(Object json)
Note: If the schema is synchronous, this method will call internally
json
- input to validateValidationException
if json doesn't match the schema, otherwise a succeeded future.public void validateSync(Object json)
ValidationException
if json doesn't match the schema.json
- input to validatepublic JsonPointer getScope()
public Object getJson()
public boolean isSync()
Copyright © 2021 Eclipse. All rights reserved.