What are possible negative effects of replacing geode-json.jar with a different implementation of the org.json package? I'm currently using version 1.6, but have plans to move to latest available.
I ask because I have a conflict in requirements. My application makes use of Geode Regions as a distributed data Map, but also needs to be able to convert a Set<String> to JSON and back. When using the geode-json.jar, the conversion from Set to JSON results in a String : "[one, two, three]", but converting that "String" back to a Set requires modification of the String. When I use alternate JSON implementations, the conversion from Set to JSON results in a Collection of String : ["one", "two", "three"], which converts back to a Set directly I do not have any plans to store native JSON documents in Geode Regions. I build my applications as a Spring-Boot fat jar and consume the geode-json.jar as a transitive dependency from geode-core.jar. Thanks, George.
