Resolve BankOfCorda through NMS in protocol
Fixes following Integration testing.
Register custom RPC Kryo classes.
Protocol -> Flow renaming
Bank of Corda demo - Issuer of Cash
Resolve BankOfCorda through NMS in protocol
Fixes following Integration testing.
Protocol -> Flow renaming
Addressed all comments in PR review.
Removed bank lines.
Updated minor inconsistency in README.md
All protocol references changed to flow.
changed protocol -> flow in TODO comment.
changed startProtocolPermission -> startFlowPermission in README.md
Added transaction id to IssuerFlow Success response.
Removed explicit call to record Cash Move transaction (as already recorded in subflow)
Removed quasar dependency.
Addressed comment in PR.
Updated to use CompositeKey.
Added arguments to pass in Currency and Amount.
Updated run configurations to pass in Currency and Amount values
Added additional parameter to IssuerFlow request: issueToPartyReference
Added Vault updates verification in RPC Integration test.
Fixed RPC Integration test (Vault assertions)
Updated run-time dependencies in line with other demos.
Applied changes following PR review (exception handling, party resolution handling, docs)
Updated gradle client run configs with new parameters.
Main driver app now uses standard out for display (was using logger info() but nothing was being displayed because of restrictive config)
Fixed formatting display problems.
Updated Web Api code to use new CordaRPCOps interface (and new partyFromName() exposed method)
Removed unused import.
* Reordered functions in the network map visualiser as a part of an ongoing refactor.
* Started separating concerns out of the NetworkMapVisualiser.
* Moved more view logic to the view class.
* Split out some of the progress tracker visual logic out into the view.
* Finished partial refactor to push model data into the model class.
* Moved some more view and model logic from controller to model.
The RPC mechanism uses message queues and is essentially conventional except for the fact that it supports marshalling observables. An observable encapsulates a stream of ongoing events, and server-side observables sent to the client are automatically bound to message queues and managed by Artemis.
This moves a lot of the test support code into its own package which is only imported for tests,
so it's not shipped as a part of core Corda. The node currently depends on this support code to
compile, although future work could try to separate this out. This change highlights that parts
of production code is dependent on test elements (i.e. dummy keys), and makes it harder for
such accidental crosses to occur later.
An integration test category is also added as part of this work, to contribute towards COR-345.
