json-schema-validator | JSON Schema Validator | Plugin library

Like code organization, there is no one right answer. If you are going to reuse a particular schema in a number of different environments, putting it in a separate file can make sense. But if you're only going to use it in one place, it may be more convenient to put it under a $defs in the same file. You could even give that schema a nicer name to reference it, via $anchor.

Allure jenkins install config

I found the answer by myself, this is some kind of issue in fresh versions of allure-commandline, try to :

1. install old version, for instance 2.8.0
2. then you could install any new version

Seems like in old version, while installation, it's creating path(for ubuntu in my case) in correct direction, and then just update with a new one... Or you can insert installation directory manually and initially install a new version

• Explanation

I believe you are using wso2am-3.1.0 vanilla pack along with a custom sequence file which probably has a mediator using "json-eval($.)" expression. Please confirm. This is a known issue in the wso2am-3.0.0 and wso2am-3.1.0 vanilla packs.

This is becasue when we use json-eval($.) expression in a sequence in the /repository/deployment/server/synapse-configs/default/sequences directory and when it gets deployed, the synapse is setting the GsonJsonProvider [1] to represent the JSON inside the Jayway JsonPath[2].

Since the GsonJsonProvider is getting loaded, even if we remove the particular sequence file which has the json-eval($.) expression in a property mediator, the issue will still persists until we restart the server.

But, if we do not use the json-eval($.) expression at all in a sequence in the /repository/deployment/server/synapse-configs/default/sequences directory, we will not get the above error when we enable the JSON schema validation as the jsonsmartjsonprovider [3] is used to represent the JSON inside the Jayway JsonPath.

Since the JSON object representation is getting different in the error scenario, it throws the IllegalArgumentException in that case.

• Solution

You can approach one of the following solution as suggested below.

1. This issue has been fixed in the latest WUM/updated pack. If you have the WSO2 subscription then you can get the latest update.
2. You can deploy a new wso2am-3.1.0 vanilla pack and invoke the API calls without the sequence having json-eval($.) expression.

[1] https://www.javadoc.io/doc/com.jayway.jsonpath/json-path/latest/com/jayway/jsonpath/spi/json/GsonJsonProvider.html

[2] https://github.com/wso2/wso2-synapse/blob/417ce10dec58579b758e12f41909f17c09d25a64/modules/core/src/main/java/org/apache/synapse/mediators/eip/EIPUtils.java#L348

[3] https://www.javadoc.io/doc/com.jayway.jsonpath/json-path/latest/com/jayway/jsonpath/spi/json/JsonSmartJsonProvider.html

It's possible to remove all external references (references to other schema documents). This is generally referred to a schema bundling. However, it's not always possible to remove all local references (references within the same schema document like to $defs/definitions).

Bundling is actually really easy. Here are some references.

• https://json-schema.org/understanding-json-schema/structuring.html#bundling
• https://json-schema.org/blog/posts/bundling-json-schema-compound-documents

Inlining local references ranges from trivial to hard to impossible. If there are no references in the sub-schema being inlined, then a simple replacement can work. If the sub-schema being inlined has references, you might have to rewrite those references because their target might have been moved as well. If the schema is recursive, the fully inlined schema would be infinitely large. Of course you could limit the recursion depth and only have a very large schema instead of an infinitely large schema.

So, if your tooling doesn't handle local references, it's pretty much useless and there's not much you can do. If your tooling just doesn't handle external references, that shouldn't be a problem. It's easy enough to bundle a schema by hand. You don't even need additional tooling.

I had this same problem! The easiest solution for my case was to just use a Java 1.8 project - Heroku auto defaults to 1.8.

According to the Java Heroku docs here, the supported version are as follows:

• Java 7 - 1.7.0_312
• Java 8 - 1.8.0_302
• Java 11 - 11.0.12
• Java 13 - 13.0.8
• Java 15 - 15.0.4
• Java 16 - 16.0.2

It seems you're using Java 11. To tell Heroku this, make a file called system.properties in your resources folder. In system.properties, add java.runtime.version=11. I believe you can also do java.runtime.version=11.0.12.

Hope this helps! Review the docs for more information.

The specification states that the default value must match the first element of the union: https://avro.apache.org/docs/current/spec.html#Unions.

Therefore you need to change the order of your union to have the null type first, or change the default to be an integer type.

java-json-tools/json-schema-validator seems not to have been updated for some time. I'd probably pick one of the libraries listed here. These two seem to be most actively maintained: everit-org/json-schema and networknt/json-schema-validator.

networknt/json-schema-validator works with Jackson, which is one of the most popular JSON libraries in the Java world, so it should suit your needs. Here's a simple example of how you could validate a JSON object and print errors (I omitted error handling for the sake of simplicity):

It was news to me, but according to the spec it does seem that objects are valid enum values. That said, your usage is quite unusual. I've not seen it used before.

the six primitive types ("null", "boolean", "object", "array", "number", or "string") ...

6.1.2. enum ...

Elements in the array might be of any type, including null.

Your problem is fundamentally that the library that you're using doesn't know how to convert those objects to printable strings. Even if it did give it a reasonable go, you might end up with

The JSON Schema spec (all drafts) says that unknown keywords are to be ignored. The meta-schema not having "additionalProperties": false is correct.

I can't speak to this implementation specifically, but this is likely what's happening.