ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-21 05:53:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
6c4ab9a440
corda/samples/trader-demo
History
Arshad Mahmood 6dd33fb8f7 Upgrade to gradle 7.6, kotlin 1.8 and jdk 17 
Major changes due to JDK 17:
1. JDK17 JCE Provider now has built-in support for eddsas, corda uses
   the bouncycastle (i2p) implementation. This PR removes the conflicting
   algorithms from the built-in JCE provider.

2. JavaScript scripting has been removed from the JDK, the corda log4j config was using
   scripting to conditionally output additional diagnostic info if the MDC
   was populated. This PR has removed the scripting.

3. The artifactory plug-ins used are now deprecated, this PR has removed them
   and uses the same code as Corda 5 for publishing to artifactory.

4. Javadoc generation has been modified to use the latest dokka plug-ins.

5. Gradle 7.6 has implemented an incredibly annoying change where transitive
   dependencies are not put on the compile classpath, so that they have to be
   explicitly added as dependencies to projects.

6. Mockito has been updated, which sadly meant that quite a few source files
   have to changes to use the new (org.mockito.kotlin) package name. This makes
   this PR appear much larger than it is.

7. A number of tests have been marked as ignored to get a green, broadly they fall
   into 3 classes.

   The first is related to crypto keypair tests, it appears some logic
   in the JDK prefers to use the SunJCE implementation and we prefer to use
   bouncycastle. I believe this issue can be fixed with better test setup.

   The second group is related to our use of a method called "uncheckedCast(..)",
   the purpose of this method was to get rid of the annoying unchecked cast compiler
   warning that would otherwise exist. It looks like the Kotlin 1.9 compiler type
   inference differs and at runtime sometimes the type it infers is "Void" which causes
   an exception at runtime. The simplest solution is to use an explicit cast instead of
   unchecked cast, Corda 5 have removed unchecked cast from their codebase.

   The third class are a number of ActiveMQ tests which appear to have a memory leak somewhere.
2023-11-06 10:24:17 +00:00
..
src ENT-6374 - Fix slf4j warning in trader-demo (#6971) 2021-10-18 11:59:51 +01:00
workflows-trader Upgrade to gradle 7.6, kotlin 1.8 and jdk 17 2023-11-06 10:24:17 +00:00
build.gradle Upgrade to gradle 7.6, kotlin 1.8 and jdk 17 2023-11-06 10:24:17 +00:00
README.md make usage of flow overrides more explicit in documentation for trader-demo 2019-01-17 11:22:06 +00:00

README.md

Trader demo

This demo brings up five nodes: Bank A, Bank B, Bank Of Corda, NonLogging Bank and a notary node that they all use. Bank A will be the buyer, and requests some cash from the Bank of Corda in order to acquire commercial paper from Bank B, the seller.

The NonLogging Bank node is present to demonstrate the usage of the "Configuring Responder Flows" feature of Corda described here. The override is defined within the deployNodes section of the build.gradle. In this case, we are overriding the default responder for net.corda.traderdemo.flow.SellerFlow to be a version that does not print out information about the transaction.

    node {
        name "O=NonLogging Bank,L=London,C=GB"
        p2pPort 10025
        rpcUsers = ext.rpcUsers
        rpcSettings {
            address "localhost:10026"
            adminAddress "localhost:10027"
        }
        extraConfig = ['h2Settings.address' : 'localhost:10035']
        flowOverride("net.corda.traderdemo.flow.SellerFlow", "net.corda.traderdemo.flow.BuyerFlow")
    }

To run from the command line in Unix:

  1. Run ./gradlew samples:trader-demo:deployNodes to create a set of configs and installs under samples/trader-demo/build/nodes
  2. Run ./samples/trader-demo/build/nodes/runnodes to open up five new terminals with the five nodes
  3. Run ./gradlew samples:trader-demo:runBank to instruct the bank node to issue cash and commercial paper to the buyer and seller nodes respectively
  4. Run ./gradlew samples:trader-demo:runSeller to trigger the transaction. If you entered flow watch, you can see flows running on both sides of transaction. Additionally you should see final trade information displayed to your terminal

To run from the command line in Windows:

  1. Run gradlew samples:trader-demo:deployNodes to create a set of configs and installs under samples\trader-demo\build\nodes
  2. Run samples\trader-demo\build\nodes\runnodes to open up five new terminals with the five nodes
  3. Run gradlew samples:trader-demo:runBank to instruct the buyer node to request issuance of some cash from the Bank of Corda node
  4. Run gradlew samples:trader-demo:runSeller to trigger the transaction. If you entered flow watch, you can see flows running on both sides of transaction. Additionally you should see final trade information displayed to your terminal