ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-29 17:28:56 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

ENT-4107: Document blob inspector issue (#5685)

Browse Source 
* ENT-4107 - document issue with enums in the blob inspector (#5685)

* ENT-4107 - fixed formatting
This commit is contained in:
Tudor Malene 2019-11-06 17:04:05 +00:00 committed by Jonathan Locke
parent 0445fac0e5
commit b1e5b659c1
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/source/blob-inspector.rst
View File

@ -91,6 +91,17 @@ Here's what a node-info file from the node's data directory may look like:
Notice the file is actually a serialised ``SignedNodeInfo`` object, which has a ``raw`` property of type ``SerializedBytes<NodeInfo>``. Notice the file is actually a serialised ``SignedNodeInfo`` object, which has a ``raw`` property of type ``SerializedBytes<NodeInfo>``.
This property is materialised into a ``NodeInfo`` and is output under the ``deserialized`` field. This property is materialised into a ``NodeInfo`` and is output under the ``deserialized`` field.
Classpath
~~~~~~~~~
If you run the blob inspector without any JAR files on the classpath, then it will deserialize objects using the Class Carpenter (see :doc:`serialization` for details).
The reason for this is that the types are not available, so the serialization framework has to synthesise them.
.. note:: This mechanism works fine in most situations, but there is one known issue when the serialized blob contains an ``enum``.
In this case you will get this exception ``java.lang.NoClassDefFoundError: Could not initialize class _YourEnum_``.
To solve this problem, you must add the JAR file that contains the ``enum`` to the classpath of the blob inspector.
Command-line options Command-line options
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~