...
87a0a8c7505d641/7org.infinispan.schematic.internal.SchematicEntryLiteral6org.infinispan.marshall.jboss.JBossExternalizerAdapterq externalizer$org.infinispan.marshall.ExternalizerDorg.infinispan.schematic.internal.SchematicEntryLiteral $Externalizer7org.infinispan.schematic.internal.SchematicExternalizer8org.infinispan.schematic.internal.document.BasicDocument;?org.infinispan.schematic.internal.document.DocumentExternalizer2; 23metadata?id87a0a8c7505d64/contentTypeapplication/jsoncontent>propertiesghttp://www.jcp.org/jcr/1.0FprimaryType$namemode:rootuuidroot3uuid 87a0a8c7505d64/children034<key87a0a8c317f1e7jcr:systemnamejcr:system1Skey387a0a8c7505d64 53f49a07-8e14-41a1-bab3-abc59d86846enamechandni45 |
Some of these elements are:
87a0a8c7505d64 refers to root node UUID
The grayed out text refers to Modeshape classes responsible for data representation and serialization. The serialization is done by the framework JBoss Marshalling, which can be configured to use custom serialization classes that read and write content in the format of their choosing (in this case it's BSON). The serialization format contains the name of datastructures and ModeShape custom marshallers (classes in org.infinispan.schematic.internal.*)
- Node name.
- The file contains binary data for specifying different internal attributes, so the file might show garbage characters or numbers in strings. /children0<key87a0a8c317f1e7jcr:systemnamejcr:system1Skey387a0a8c7505d64 . Similarly, if object 'chandni' had siblings, the array would appear in the binary as:
- Name/string Node children UUID and name (6988a17a-ad2f-48f6-aef5-e7d411e184d9namechandni)
...