I raised the issue for this https://github.com/FasterXML/jackson-module-jsonSchema/issues/141
Given that this change has not been picked up yet, I am trying to see if any one wants to join hands on this change. I am planning to start work on this. If anyone has made attempt in this regard, please let me know. Following is summary of my evaluation so far. Breaking changes between 3 and upward are minimal. For example, required field got changed from boolean to array at object type. Locally, when I removed the required attribute from JsonSchema and put at ObjectSchema level, parsing happened correctly. Given that Json specs has tendency to break the compatibility, I recommend to have types per schema version even if it means code duplication similar to apache commons approach. This will ensure that each version implementation stay independent and not causing regression in older implementation. mbknor <https://github.com/mbknor> seems to have spent lot of time analyzing and trying to reuse existing but finally gave up and wrote a totally different implementation in scala https://github.com/mbknor/mbknor-jackson-jsonSchema Based on his experience, I am recommending cloning the spec 3 implementation, copy for new version and try not reusing types between the version. We can refactor to use classes that has lot of logic so that those stays common across different version. Please let me know if any one has other thoughts on how to add support for new version. I am open to any idea that can make supporting new spec version seamless. -Rajnish -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/3f64c7cd-d10b-4c50-91d6-fbdb252456d3n%40googlegroups.com.
