...
Caused by: org.apache.geode.pdx.JSONFormatterException: Could not parse JSON document: [Source: (String)"{"@type":"example.app.model.Customer","id":1,"name":"Jon Doe"}"; line: 1, column: 63]
...
Caused by: org.apache.geode.cache.CacheClosedException: Client pools have been closed so the PDX type registry is not available.
-
DONE - Test using @EnableClusterAware annotation (this is currently not working because the "Cluster Configuration Push" happens in the SmartLifecycle phase of container startup and the "Import" happens in the BeanPostProcessor.postProcessAfterInitialization() callback on the Region, which occurs before the push... #sigh)
-
DONE - Test using @EnableCachingDefinedRegions annotation (i.e. Regions created from Spring's Cache Abstraction annotations or JSR-107, JCache API annotations)
-
Test using @EnableClusterDefinedRegions annotation (i.e. Regions created on the client from the server Region definitions)
-
Test export/import with entity having natural id (e.g. Book.isbn) that would need to include a @identifier JSON object metadata field. Possible for POJO stored in the Region since we can inspect the object class type, not possible when the Region value is a PdxInstance that did not originate from JSON. In that case, the user must manually make sure the non-JSON generated PdxInstance includes a @identifier PDX field before it is exported to JSON.
-
Add more documentation around features & limitations (gotchas):
** Java 8 Types, JSR-310 (Time) Types and Jackson 2 vs. 3, etc.
** Use of multiple Cache Data Importers and ordering using the @Order annotation or the Ordered interface on Cache Data Importer/Exporter bean definitions.
** Explain the (hidden) use of Predicate's to filter Regions on import and export.
** Explain the API/SPI for writing extensions, such as Cache Data Importers/Exporters for XML,
XLS, SQL DML or other data formats.
** Explain the types of numeric values: e.g. application domain model class (e.g. Customer) might define an id field of type Long but the value for the corresponding JSON field (i.e. "id") will be a byte as processed by JSONFormatter, therefore Region.get(key) lookups must be customersRegion.get((byte) 1) even if the "Customers" Region is defined as Region<Long, Customer>. Also the Region entry value will be a PdxInstance and not Customer.
** ???
-
???
The following things need to be investigated further:
ClientCacheand client LOCALRegion(s)with no connections (i.e. noPooldefined) to a cluster/server using PDXCurrently Throws:
:(
DONE - Test using
@EnableClusterAwareannotation (this is currently not working because the "Cluster Configuration Push" happens in theSmartLifecyclephase of container startup and the "Import" happens in theBeanPostProcessor.postProcessAfterInitialization()callback on theRegion, which occurs before the push... #sigh)DONE - Test using
@EnableCachingDefinedRegionsannotation (i.e.Regionscreated from Spring's Cache Abstraction annotations or JSR-107, JCache API annotations)Test using
@EnableClusterDefinedRegionsannotation (i.e.Regionscreated on the client from the serverRegiondefinitions)Test export/import with entity having natural id (e.g.
Book.isbn) that would need to include a@identifierJSON object metadata field. Possible for POJO stored in theRegionsince we can inspect the object class type, not possible when theRegionvalue is aPdxInstancethat did not originate from JSON. In that case, the user must manually make sure the non-JSON generatedPdxInstanceincludes a@identifierPDX field before it is exported to JSON.Add more documentation around features & limitations (gotchas):
** Java 8 Types, JSR-310 (Time) Types and Jackson 2 vs. 3, etc.
** Use of multiple Cache Data Importers and ordering using the
@Orderannotation or theOrderedinterface on Cache Data Importer/Exporter bean definitions.** Explain the (hidden) use of
Predicate'sto filterRegionson import and export.** Explain the API/SPI for writing extensions, such as Cache Data Importers/Exporters for XML,
XLS, SQL DML or other data formats.
** Explain the types of numeric values: e.g. application domain model class (e.g.
Customer) might define anidfield of typeLongbut the value for the corresponding JSON field (i.e. "id") will be abyteas processed byJSONFormatter, thereforeRegion.get(key)lookups must becustomersRegion.get((byte) 1)even if the "Customers"Regionis defined asRegion<Long, Customer>. Also theRegionentry value will be aPdxInstanceand notCustomer.** ???
???