ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-30 09:48:59 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
7019ea8e47
corda/samples/cordapp-configuration
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/main/resources Upgrade to gradle 7.6, kotlin 1.8 and jdk 17 2023-11-06 10:24:17 +00:00
workflows 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 Fixed the CorDapp configuration demo (#2967) 2018-04-16 17:23:11 +01:00

README.md

Cordapp Configuration Sample

This sample shows a simple example of how to use per-cordapp configuration. It includes;

  • A configuration file
  • Gradle build file to show how to install your Cordapp configuration
  • A flow that consumes the Cordapp configuration

To run from the command line in Unix:

  1. Run ./gradlew samples:cordapp-configuration:deployNodes to create a set of configs and installs under samples/cordapp-configuration/build/nodes
  2. Run ./samples/cordapp-configuration/build/nodes/runnodes to open up three new terminals with the three nodes
  3. At the shell prompt for Bank A or Bank B run start net.corda.configsample.GetStringConfigFlow configKey: someStringValue. This will start the flow and read the someStringValue CorDapp config.

To run from the command line in Windows:

  1. Run gradlew samples:cordapp-configuration:deployNodes to create a set of configs and installs under samples\cordapp-configuration\build\nodes
  2. Run samples\cordapp-configuration\build\nodes\runnodes to open up three new terminals with the three nodes
  3. At the shell prompt for Bank A or Bank B run start net.corda.configsample.GetStringConfigFlow configKey: someStringValue. This will start the flow and read the someStringValue CorDapp config.