datanucleus / datanucleus-json Goto Github PK

See datanucleus/datanucleus-core#81

We currently make use of org.json definition of JSONObject, JSONArray etc, but JSR0353 provides javax.json. Would make sense to migrate to this at a convenient point.

See
http://www.javabeat.net/2013/10/java-json-api-jsr-353/
http://www.javabeat.net/2013/10/json-processing-javaee-7-object-model-api/

The downside of using javax.json is that we need only 5 classes currently and these are repackaged internally. Using javax.json will require a user to have javax.json and an implementation of that API in their CLASSPATH

Hi, Thanks for all your effort. Can i know whether the JSON Persistence can be used to integrate with Apache SeaweedFS storage or Minio apart from the S3. Or Do we need to create a different Persistence like Google storage. Thanks in Advance for answering my query.

When we execute a query and use FetchFieldManager, we have to use the constructor for an ExecutionContext (i.e ObjectProvider not yet known). This means that we cannot easily wrap any SCO fields in FetchFieldManager. Consequently we need to call

ObjectProvider.replaceAllLoadedSCOFieldsWithWrappers()

just after the FetchFieldManager process.

Refer to core issue 19

When we retrieve a List from JSON we retrieve it in the exact same order as persisted. That is, it is stored as a Collection in the owner object. If a user puts some @orderby annotation they may want the list reordering.

This applies to ALL non-RDBMS datastores, so creating some generic code would make sense and reorder them in-memory, maybe using a Comparator.

Refer to datanucleus/datanucleus-core#134