* Pull out and tidy type parameter inference
* Contain null proliferation
* Extract fingerprinter state
* SerializerFingerPrinter is always initialised with a SerializerFactory
* Move non-recursive state transition functions into state
* Move all state transition functions into state
* Simplify and optimise with mutable state
* Move TypeParameterUtils back into internal.amqp
* Clarify behaviour of constructorForDeserialisation
* constructorForDeserialization no longer returns null
* Capture field properties
* Narrow PropertyDescriptor
* Use map rather than apply on a mutable list
* Remove printStackTrace added for debugging
* CORDA-1869 minor tweaks
* Use groupingBy to avoid creating an intermediate map
* Convert some functional origami to plain old for-loops
* Eliminate nested lambda to unbreak pre-serialisation
* Use EnumMap for map of Enums
* Add named caches and apply to NonInvalidingUnboundCache and all usages.
* Add named caches and apply to NonInvalidingCache and all usages.
* Add named caches and apply to NonInvalidingWeightBasedCache and all usages.
* Move NamedCache to core/internal
* Remove type `NamedCache` and `NamedLoadingCache`
* Suppressed 'name not used' warning, added comment, and fixed generic parameters on the buildNamed functions.
* Use `buildNamed` in all caffeine instances in production code. Not using it for caches that are created in test code.
* Add checks for the cache name
* Formatting
* Minor code review revisions
* CORDA-1672 - Enable better user-helpful error messages
The issue is that the error reporting framework in the serializer is
targeted at developers in the node. However, because we pass exceptions
to users over RPC those error messages aren't always helpful.
Keep an internal exception that tracks debug useful information and log
that just before any exception escapes the framework and allow for
specific user "problem mitigation" issues to be set.
* wip
* update remaining excepions
Moved start up logic of the various node components out of their c’tors and into “start” methods, which are called from Node.start(). The components themselves are created in the Node’s c’tor with minimal initialisation logic.
Certain things are not immediately available at construction time, which are instead given to the components at start time in an orderly fashion:
* Certs from the node’s key store and trust store
* The network parameters, and thus access to things like maxMessageSize and the contracts whitelist
* A running database - several components were doing database stuff their c’tors
* The node’s NodeInfo, and thus access to things like identities and addresses
The messaging service couldn’t be created in the Node’s c’tor due to initialisation issues with MockNode. This should be fixed in a later commit.
* Reduce ProGuard output for kotlin-metadata artifact.
* Configure ProGuard not to display "notes" about potential configuration issues. Keep notes for the "checkDeterminism" steps, though.
* Also resolve some of the issues that we would now be ignoring.
Nullability logic was relying on annotations that Kotlin applies by
default but is left to the developer in Javaland. Change this around
so it works for both.
In Kotlin, the property must be nullable, in Java, it can't be a
primitive.
* CORDA-1661 Reverting DEV certificates
* Addressing review comments
* Removed the intermediate certificate from the trust store and added some test cases for the revocation check
This requires the class carpenter to be able to run in a "lenient" mode where it permits synthesised classes to implement interfaces with unimplemented methods.
* Fix issue when evolving enums with transformation chains
* Regenerate test data for deserializeWithRename test and unignore
* Further tweaks / remove debugging
* Formatting tweaks
* Address review comments
* Remove debug
* Add classname to serialization tranform exceptions
* Use direct node links instead of indexes to improve readability
* More readability tweaks
* More readability improvements
* rename require to requireThat to resolve conflict with kotlin libraries
* Add logging of error message
* Change requireThat helper to inline function
* remove unneeded toString
* Further tweaks
* Change NotSerializableException to more generic IOException
* Make exception context clearer
