-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in -core: URI normalization fails with URNs/"opaque" URIs (was Validation breaks when using Jackson >= 2.4.2) #119
Comments
You are indeed correct; and there are two problems here...
|
So we use the Jackson ObjectMapper class to generate the schema.
All classes in the code come from package com.fasterxml |
Hm, missed the initialization of the ObjectMapper om:
|
OK, I found the source of the bug; the normalizer method that I use seems to be broken for this particular type of URI... Now working on fixing it... |
The source has been found: java-json-tools/json-schema-core@8d258e3 Specifically, in your case, the URI has a scheme but all other .get*() for the URI class (safe for .getSchemeSpecificPart()) are null. So, this is really a bug in -core, which also affects -validator. |
OK, issue is fixed in -core. Since this requires a dependency update in the build file, I'll close this issue when a new -core version is available. |
Great, thx. Sorry for not providing a reproduction example up front. |
Any concrete plans for the next core release? |
Fixed with new version 2.2.6 (which is now published) |
Is this fixed for draft 3 schema file as well? --- BEGIN MESSAGES --- |
@njaiswal that's not the same problem at all you have here, look at what the error message says carefully... |
For us, tests break with weird Exception at bottom.
I notice that the schema we generate using Jackson 2.4.3 now has additional lines:
The new line with
urn:
seems a likely cause.Not sure how to best reproduce this.
Exception:
The text was updated successfully, but these errors were encountered: