jackson-module-jsonSchema icon indicating copy to clipboard operation
jackson-module-jsonSchema copied to clipboard

Module for generating JSON Schema (v3) definitions from POJOs

Results 40 jackson-module-jsonSchema issues
Sort by recently updated
recently updated
newest added

According to : http://spacetelescope.github.io/understanding-json-schema/reference/generic.html#metadata along side "description" we also should be able to define the "title" property. For description, this is achievable using @JsonPropertyDescription("..."). We should consider adding another annotation...

JSON can have number values outside the range of double. Also, it's important that multipleOf have an exact representation to be interpreted correctly. BigDecimal is better for these reasons.

This pull request is somehow related to https://github.com/FasterXML/jackson-module-jsonSchema/pull/32 but it allows to resolve described problem quite differently. We run into a situation where we needed to filter out some bean...

A JSON Schema specification could be easily extended to add custom properties (see json-schema/json-schema/issues/187). How can I achieve this with Jackson? I'm trying to use a custom `SchemaFactoryWrapper` but I...

I have two classes: `Article` and `User` and their respective schemas are available at: - http://localhost:8080/api/articles/$schema - http://localhost:8080/api/users/$schema Since `Article.author` is of type `User`, how can I have the correct...

I'm using the `HyperSchemaFactoryWrapper` to generate schema `links`, now I'd like to add validation patterns through `ValidationSchemaFactoryWrapper` and write some other wrappers for additional properties. Is it possibile? I'm using...

[Section 4.3](http://json-schema.org/latest/json-schema-hypermedia.html#anchor10) of the JSON Schema specification mentions the `media` property, which is used to give additional hints about the semantics of non-JSON data that is encoded as a JSON...

I'm doing an implementation of Swagger 2.0, and Swagger uses JSON Schema to describe not only incoming and outgoing JSON, but also the constraints on any parameters in your REST...

I have the following Java enum: @XmlType @XmlEnum(Integer.class) public enum DefaultMessageVersion { @XmlEnumValue("1") ONE; } That is producing the following json schema snippet: "defaultMessageVersion" : { "type" : "string", "enum"...

This shouldn't be too bad. I'm leaving an issue to remind myself to do it.

enhancement