Post by dyutiman on Dec 6, 2019 12:09:16 GMT
Hi,
What I am trying to do is to dynamically generate Java classes from the schema files. For that I am using jsonschema2pojo library. In the process one issue I hit with the properties referenced by a schema with remote url. For example, in the ComputerSystem schema the Memory property is referenced by redfish.dmtf.org/schemas/v1/MemoryCollection.json#/definitions/MemoryCollection.
"Memory": {
"$ref": "http://redfish.dmtf.org/schemas/v1/MemoryCollection.json#/definitions/MemoryCollection",
"description": "The link to the collection of memory associated with this system.",
"longDescription": "This property shall contain a link to a Resource Collection of type MemoryCollection.",
"readonly": true,
"versionAdded": "v1_1_0"
}
If I am seating in a network which does not have outbound connection, then the tool will not be able to use the external reference. And hence the property type in my Java class will be the plain java.lang.Object. This is not desirable as, those properties should have the proper type. For example in this case the Memory property should be the MemoryCollection object type.
I just wanted to check if there is any particular reason for which some of these properties are referenced by external URLs! Or is there any other way to work around on this issue! Those properties with local references are coming up perfectly fine.
- thanks
What I am trying to do is to dynamically generate Java classes from the schema files. For that I am using jsonschema2pojo library. In the process one issue I hit with the properties referenced by a schema with remote url. For example, in the ComputerSystem schema the Memory property is referenced by redfish.dmtf.org/schemas/v1/MemoryCollection.json#/definitions/MemoryCollection.
"Memory": {
"$ref": "http://redfish.dmtf.org/schemas/v1/MemoryCollection.json#/definitions/MemoryCollection",
"description": "The link to the collection of memory associated with this system.",
"longDescription": "This property shall contain a link to a Resource Collection of type MemoryCollection.",
"readonly": true,
"versionAdded": "v1_1_0"
}
If I am seating in a network which does not have outbound connection, then the tool will not be able to use the external reference. And hence the property type in my Java class will be the plain java.lang.Object. This is not desirable as, those properties should have the proper type. For example in this case the Memory property should be the MemoryCollection object type.
I just wanted to check if there is any particular reason for which some of these properties are referenced by external URLs! Or is there any other way to work around on this issue! Those properties with local references are coming up perfectly fine.
- thanks
