Ability to use an opaque namespace? about json-schema-validator

[fge]

Hello,

First, thank you for the appreciative comments!

There is a hack in the code, in JsonRef, so as to deal specifically with jar URIs, so it seems it is not plugged where you expect. Hmm. I'll have to devise a test.

I have two questions:

1. how do you define an opaque URI? I have always had trouble with that;
2. is your jar in the classpath? If yes, can't you use:

// Note the final /
new JsonSchemaFactory.Builder().setNamespace("resource:/base/path/to/schemas/")

?

[bpfoster]

Aha! - I knew I had to be missing something stupid simple. Yes, using a resource:/path/to/schemas/ namespace works perfectly for this! Thank you!

I will admit that the idea of an opaque URI was new to me when starting this, so I have to rely on the Javadoc:

An opaque URI is an absolute URI whose scheme-specific part does not begin with a slash character ('/')

vs a hierarchical:

A hierarchical URI is either an absolute URI whose scheme-specific part begins with a slash character, or a relative URI, that is, a URI that does not specify a scheme

So in this case we have 2 URIs: jar:file:/path/to/jarfile!/path/inside/jar/ , and resource:/path/inside/jar/. Based on the documentation, I take it to mean the scheme in the first is jar: and the second is resource:. The next character (beginning the 'scheme-specific part'), respectively, is f and /, thus making the first opaque and the second hierarchical.

Thank you so much for the quick pointer!

[fge]

Glad to know it worked!

However, I still think there is a bug. You can, indeed, do:

final JsonSchema schema = factory.fromURI("jar:file:/foo/bar.jar!/path/to/schema");

and, in this case, $ref will also work. Setting a "jar" namespace and loading a schema, however, will not.

I have to think abouti it some more.