-
Notifications
You must be signed in to change notification settings - Fork 282
jackson as the JSON parser instead of org.json #189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @ramuramaiah , thank you for your efforts. This sounds promising, though I doubt it doesn't break any of the method signatures. Please create a fork of this project and share your changes in the form of a pull request. If you are not familiar with this workflow please refer to the GitHub documentation . Making the json implementation replaceable has been under consideration for quite some while, but for me it doesn't look simple to replace the data model of the library in a backward-compatible way (which is a top-priority for the project). I'm curious about what you figured out. Thanks. |
erosb, |
You have to go to the GH page of your fork and find the Pull Request button there. |
erosb, Replaced the org.json JSON parser with jackson JSON parser #190 |
@ramuramaiah Is it possible to create a fork and implement your changes into that fork? I also need this functionality as for now it is giving me a lot of headache to let the code work with existing POJO's and with Jackson |
@Yobikap if you need jackson then TBH I would look for an other json schema library. There are a few options nowadays. |
Hello, this project is now superseded by erosb/json-sKema which has its own json parser and doesn't have such library dependency. Closing this issue. |
Hi,
I have modified the original source code of everit JSON schema parser to make use of jackson as the underlying JSON schema parser instead of org.json due to the business unfriendly license of org.json JSON parser.
I have made sure the following
Let me know if I can share the changes and anyone is interested to make use of the same.
I am not sure about the copyrights etc. Hence I don't want to create a new GitHub project.
The text was updated successfully, but these errors were encountered: