* ENT-2293: Skeleton of the new "rpcWorker" module
* ENT-2293: Add first failing test
(RPC server has not been implemented or started yet)
* ENT-2293: Further progress to start RPC server (unfinished)
* ENT-2293: RPC server started to work.
* ENT-2293: Slim down RpcWorker.
* ENT-2293: Minor changes.
* ENT-2293: Minor refactoring
* ENT-2293: Expand test coverage.
* ENT-2293: Introduce PicoCli for command line parsing.
* ENT-2293: Changes to make RPC server actually start.
* ENT-2293: Create simple RPC client.
* ENT-2293: Initialize serialization outside of RpcWorker.
* Feature/corda 1813/change postgres column type (#3631)
* CORDA-1813 fix Postgres db bloat issue
* CORDA-1813 merge fixes
* CORDA-1813 change column type and size to a standard corda type
* CORDA-1813 docs
* CORDA-1813 create custom hibernate type for the checkpoint blob and align with enterprise
* CORDA-1813 Remove max col size
* CORDA-1813 Remove max col size
* CORDA-1813 Fix merge
* CORDA-1813 Remove buggy :serverNameTablePrefix: configuration
* CORDA-1813 fix merge
* CORDA-1813 fix Postgres db bloat issue
* CORDA-1813 merge fixes
* CORDA-1813 change column type and size to a standard corda type
* CORDA-1813 docs
* CORDA-1813 create custom hibernate type for the checkpoint blob and align with enterprise
* CORDA-1813 Remove max col size
* CORDA-1813 Remove max col size
* CORDA-1813 Fix merge
* CORDA-1813 Remove buggy :serverNameTablePrefix: configuration
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.
* Documentation for notary health check
* Doc improvements after review
* Indent (stop messing with this, IntelliJ!)
* Ordering, correct number
* Review comments
* Moved notary healthcheck
* Rename directories and fix up build
* Moved notary healthcheck to tools
* Fix up gradle files and move long running tests to integration-test
* Add copyright headers
* Remove obsolete resource
* Break up large `call()` function, move helpers to be private in companion object
* Move ScheduledCheckFlow to its own file
* Docs etc.
* Code review: Replace magic literals by constants, enums, etc.
* Delete Readme.md (the content will be available in documentation)
* Slight refactoring of the handling flows.
* Publishing
* Fix test
* Add missing artifactory dependency
* Small documentation fixes
* Typo
The loading of all node infos in the start method was unnecessary, both for the changePublisher and _loadDBSuccess, and the setting of _registrationFuture was incorrect.
