You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From joelittl...@gmail.com on January 13, 2011 17:04:00
One important change here is to move away from using "id" to optionally specify Java type for code generation. The unique id/uri of a schema will be important when resolving refs, Having re-read the id part of the spec[1], it's clearer to me now what the intention of id is
The good news is that the core schema[2] allows additional properties for schemas themselves - so any additional meta-data can be attached to a schema.
The first step here is going to be introducing a new optional additional schema property 'javaType' that will be used to specify/override the target Java type name.
Original author: joelittl...@gmail.com (December 23, 2010 13:29:25)
A the moment jsonschema2pojo doesn't support "$ref" style syntax for referencing other schemas (see http://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.28).
Some factors to consider:
Original issue: http://code.google.com/p/jsonschema2pojo/issues/detail?id=7
The text was updated successfully, but these errors were encountered: