MappingCouchbaseConverter.write() does not provide equivalent target for lists

[vals-productions]

Simplified document:

@Document
public class Entity  {
...
	private List<EmailToken> tokenList = new LinkedList<>();

	public static class EmailToken {
		private String token;
		private String type; 
...

Saved through Repository the JSON looks like the following:

{
 ...
  "tokenList": [
    {
      "token": "G1LTUPAPVQ1JGGE",
      "type": "Type 1"
    }
  ]
... 
}

I wanted to try transaction stuff and tried to save the same object through the code suggested in docs:
Transaction Support

CouchbaseDocument entityDoc = new CouchbaseDocument(entity.getId());
mappingCouchbaseConverter.write(entity, entityDoc);
ctx.insert(
	couchbaseClientFactory.withScope("some scope").getCollection("someColl"), 
	entityDoc.getId()(), 
	entityDoc.getContent());

The result looks like the following:

{
...
  "tokenList": {
    "empty": false
  }
...
}

tokenList becomes a Map instead of a List with data loss.

[mikereiche]

Fixed in #868

Please use the latest version which is 4.4.2. https://spring.io/projects/spring-data-couchbase

Couchbase Transactions are integrated into Spring Data Couchbase beginning in 5.0.0-M5 (prerelease milestone 5)

The transactions documentation which will appear in the next release (5.0.0-M6 is currently staged at https://mikereiche.github.io/staged/ (look for the Transactions section).

There are all kinds of examples spring-data-couchbase/src/test/java in : git clone git@github.com:spring-projects/spring-data-couchbase.git. (search for test cases with 'Transaction' in the name).

[vals-productions]

I was using 4.4.0 that was supposed to have the fix. Upgraded to 4.4.2 but still get the issue. I also reproduced the issue
with List<Map<>> data structure mentioned as fixed in #868 .

I think that maybe the issue was re-introduced or not transferred into collections? As 4.0.2 is pre-collections release.

[mikereiche]

Sorry - I didn't read far enough into your post.
Use entityDoc.export() instead of entityDoc.getContent(). See #1524