So for this specific cordapp-example, after you run the nodes, you would not see net.corda.finance.flows.CashExitFlow and etc. I guess this demo code actually have two cordapps running on these nodes. So, for this tutorial, we should delete the last 5 lines of codes.
Hey,
It is Peter, I am the dev-rel person at NY office. I found the current tutorial on running example cordapp-example on IntelliJ is a bit confusing. So I add a few lines to clarify it.
* DEVREL-1297 Ledger - Doc Site Lessonly Conformance
Rewrite to bring Doc Site and Lessonly into conformance. Assumption is that Doc Site is more up to date.
* DEVREL-1297 Ledger - Doc Site Lessonly Conformance
* DEVREL-1297 Ledger - Doc Site Lessonly Conformance
Home page describes sections that link from it to enable easier navigation.
* Removed comment
* CORDA-2511 doc fix: upgrade notes for C4 need to include guidance to upgrade from C3.2 (minimum) to C4
* Addressing PR review comments.
* Addressing review comments.
* If there is no dataSourceProperties in the node.conf, the default value is modified to match the docker structure and documentation of having a persistence folder.
* chagnes according to pr review.
This allows a different signed version of the same CorDapp to be automatically trusted.
This reverts "[CORDA-2575] Allow users to whitelist attachments by public key config (#5035)"
* If there is no dataSourceProperties in the node.conf, the default value is modified to match the docker structure and documentation of having a persistence folder.
* chagnes according to pr review.
Remove some information that is way to specific for installing the
oracle jdk.
Add mention of zulu openjdk to the docs.
Specify that the docs will go through how to install the oracle jdk
only but provide links to amazon corretto, openjdk and zulu.
Also say that we support intellij 2019 which has been released now.
* CORDA-2477 Improve Signature Constraints documentation (#5041)
The Signature Constraint documentation in `api-contract-constraints`
was very limited and referred to the design doc for most information.
Information was extracted from the design doc and added to the main
documentation.
(cherry picked from commit cb85dd1e927f1bdd42ba483f53191f8be2ed4722)
* CORDA-2477 Add codesets so backported docs show properly
The Signature Constraint documentation in `api-contract-constraints`
was very limited and referred to the design doc for most information.
Information was extracted from the design doc and added to the main
documentation.
If a single whitelisted constraint is being used by input states and the version of the cordapp changes + is signed, then the constraint will transition to a signature constraint.
