Hi, thanks for your work on this project. It's useful for me to build a directory tree of swagger yaml fragments into a single swagger.yaml file, but the feature contributed in 1351309 seems to be critical to making this work perfectly. I'm currently referencing a jitpack maven repo to get a build with this commit, but would you consider publishing a release with this feature?
Thanks!

Hey,
This library was exactly what I was looking for. However, does this support getting back the file structure given a single JSON (possibly with xref pointers) or a reference file?
If not, do you plan to support this?

Use case:
I have a service that accepts JSON as a zip file and we allow the user to provide the JSON using JSONReferences. However, the internal store can be modified by other means as well (UI, etc). While returning back the zip file, we need to merge the changes and return in the same format as provided by the user.
It would be great to have this feature.

Thanks

For #3.

Support this https://tools.ietf.org/html/draft-zyp-json-schema-04#section-7.2.4

currently the version uploaded is 0.1.2, please update the latest one
https://dl.bintray.com/adjohnson916/maven/me/andrz/jackson/jackson-json-reference-core/0.1.2/

Hi,

there is an issue when putting reference in some element of an Array.
For example:
given json test.json:
[{"test": "0"},{"$ref": "external.json"},{"test": "2"}]
and external.json:
{"test": "1"}
results with:
[{"test": "1"},{"$ref": "external.json"},{"test": "2"}]

external json is resolved in first index of array and reference is still there
Is this resolvable, or in array there is some other way to place references?

Consider a less restrictive license. Look at licenses of dependencies.

Currently there is no way to use the Jacksons Paser Features (e.g. ALLOW_COMMENTS, ALLOW_YAML_COMMENTS), because the JsonContext uses its own ObjectMapper.

I would recommend set the mapper via Constructor.

In this way it is possible to use the mapper of JsonReferenceProcessor the following way

JsonContext context = new JsonContext(this.mapper, file);

With that small changes you could

• enable the Features for an ObjectMapper

• inctect this mapper in JsonReferenceProcessor like before

  I am totally new github user. Is it possible to create that feature myself?

Kind regards

Support relative JSON Pointers (https://tools.ietf.org/html/draft-luff-relative-json-pointer-00). Perhaps upstream in Jackson (FasterXML/jackson-core#228).

@fge any feedback?

I noticed you have an implementation baked into fge/json-schema-core, but it didn't look modular enough to be reused outside the context of JSON schemas.

In the README file, there is a bizarre line:

JsonReference processor = new JsonReferenceProcessor();

Which I believe it should be:

JsonReferenceProcessor processor = new JsonReferenceProcessor();

So the type returned by the constructor matches the variable's type.

UNC paths are destroyed after calling the URI#resolve method:

Example:

final URI baseUri = new File("//SERVER/some/path").toURI();
System.out.println(baseUri); // -> file:////SERVER/some/path (UNC-Path)

final URI resolved = baseUri.resolve("file.json#");
System.out.println(resolved); // -> file:/SERVER/some/file.json# (no UNC-Path)

Do you have any plans to start publishing this library to Maven Central?

I'm currently working on a Swagger validation library for which it's necessary to be able to resolve JSON refs, so it'd be great to use this library. However, I'm reluctant to ship a lib with dependencies that can't be resolved without adding repositories, as this makes life difficult for folks whose only source of Maven deps is a corporate Nexus/Artifactory installation.

I'm planning to fork this and publish it to a group I'm able to release under for now. Please let me know if this is problematic for you in any way.

Thanks,
Tom

@cowtowncoder any interest in a JSON Reference implementation for Jackson, such as this one?

I'm running this file via CLI but I just get the plain text claims. I'm doing something wrong

"claims": {
"claims": {
"claim-statement": {
"$t": "I\/We claim:"
},
"@lang": "EN",
"claim": [
{
"claim-text": {
"$t": ". A clip () for fastening a car seat cover onto a car seat, the clip () comprising:\n",
"b": [
{
"$t": "1"
},
{
"$t": "10"
},
{
"$t": "10"
}
],
"claim-text": [
{
"$t": "a head means () comprising a U-shaped holder () with a gripping means () at each end to receive and grasp a car seat cover; and",
"b": [
{
"$t": "11"
},
{
"$t": "11"
},
{
"$t": "11"
}
],
"i": [
{
"$t": "a"
},
{
"$t": "b"
}
]
},
{
"$t": "an insertion element () having a tip end, connected to the head means () via a midpoint element (), to be embedded in the car seat for fastening the car seat cover;",
"b": [
{
"$t": "13"
},
{
"$t": "11"
},
{
"$t": "12"
}
]
},
{
"$t": "characterised in that the midpoint element () is a truncated cone connecting the head means () with the insertion element (), wherein the clip () is inserted to a joining of the car seat cushion.",
"b": [
{
"$t": "12"
},
{
"$t": "11"
},
{
"$t": "13"
},
{
"$t": "10"
}
]
}
]
},
"@num": "00001",
"@id": "CLM-00001"
},
{
"claim-text": {
"$t": ". The clip () as claimed in , wherein the midpoint element () is bendable to 90°, thereby allowing different angles of insertion of the clip () onto the car seat.",
"b": [
{
"$t": "2"
},
{
"$t": "10"
},
{
"$t": "12"
},
{
"$t": "10"
}
],
"claim-ref": {
"$t": "claim 1",
"@idref": "CLM-00001"
}
},
"@num": "00002",
"@id": "CLM-00002"
},
{
"claim-text": {
"$t": ". The clip () as claimed in , wherein the clip () is made of stretchable material.",
"b": [
{
"$t": "3"
},
{
"$t": "10"
},
{
"$t": "10"
}
],
"claim-ref": {
"$t": "claim 1",
"@idref": "CLM-00001"
}
},
"@num": "00003",
"@id": "CLM-00003"
},
{
"claim-text": {
"$t": ". The clip () as claimed in , wherein the stretchable material is rubber.",
"b": [
{
"$t": "4"
},
{
"$t": "10"
}
],
"claim-ref": {
"$t": "claim 3",
"@idref": "CLM-00003"
}
},
"@num": "00004",
"@id": "CLM-00004"
},
{
"claim-text": {
"$t": ". The clip () as claimed in , wherein the insertion element () has a tip end heading downward.",
"b": [
{
"$t": "5"
},
{
"$t": "10"
},
{
"$t": "13"
}
],
"claim-ref": {
"$t": "claim 1",
"@idref": "CLM-00001"
}
},
"@num": "00005",
"@id": "CLM-00005"
}
],
"@load-source": "patent-office",
"@mxw-id": "PCLM181887614"
},
"@version": "1.0",
"@encoding": "UTF-8"
}