* Intro changes for multi node Azure deployment, more to do
* Updated text on running Azure wizard and starting writing how to use Yo CorDapp
* All text updated for Corda multi node offering in Azure
* Images for Azure multi node documentation
* Update link to Yo CorDapp video
* Fixed some typos
* Added further info on validating notary
* Changed Yo CorDapp info to manually load it since it is not pre-loaded
* Updated screenshot for Azure multi node step 2
* Uploaded yo_peers screenshot for Azure documentation
* Corda banner screenshot
* Screen shot of Corda syslog
* updated screenshot for Azure setup step3
* Updated text to account for M10 and improved notes on using Yo CorDapp
* typos fixed
* screenshot of api/yo/yos output
* Removed section on using shell because appears to crash to API
* New yo peers output screenshot
* Updated peers screenshot and example
* Minor changes following review by Joel
* Added guidance to login to portal.azure.com first
* Fix /attachments endpoint on WebServer, and update demo to use it.
* Add @Throws statements to servlet methods.
* Ensure target entry is not a directory.
* Simplify, because JarInputStream verifies signatures by default.
* Move JarInputStream.extractFile() function into core.
* Don't close the output stream automatically as it commits our response.
* Describe new source-tree directories "verifier" and "webserver", and update descriptions for "node" and "tools".
* Update changelog and release notes for M11.
* Thank Gary Rowe for his contribution to M11.
* Update Copyright and fix some broken links.
* Fix reference to CordaRPCOps class.
* Include changelog for CompositeKey upgrade.
* Fix warnings in changelog
* Update release notes after review.
* Add help for IntelliJ/Gradle.
Now builds page using kotlinx. Added support for static web content.
Removed code to re-direct to static web content if it exists.
Minor changes to comments. The recursive API crawler now uses a data class instead of a mutable map.
DemoBench: Misc usability improvements:
- Pre-fill details for some fictional banks when Add Node is pushed.
- Make services a checkbox list rather than one where you have to know how to use the keyboard to do multi-select.
- Make web server launch button spin until server is launched to show activity.
- Suppress an exception that spams the log due to inability to load all the states. It'll get fixed as part of the vault API and serialisation work.
* Subscribe to updates for transaction and vault RPCs.
* Ensure we unsubscribe our observables at the end.
* Use Rx scheduler that can observe on FX application thread.
* Add information on who started flow on a node with name where possible.
Add sealed class holding information on different ways of starting a flow: RPC, peer, shell, scheduled.
* Remove invokeFlowAsync from ServiceHub, move it to ServiceHubInternal.
We shouldn't be able to start new state machines from inside flows.
