Set the "h2.allowedClasses" system property, require database password when exposing H2 server on non-localhost address, samples start H2 server by default (reintroduces the behaviour before h2Settings.address configuration option was added)
* Move common matches to testing, add some missing ones
* Clarify test logic
* Move common matches to testing, add some missing ones
* Clarify test logic
* Rename 'randomise'
* endregion
* Fix broken unit test
* Allow MockNetwork to create StartedMockNode from UnstartedMockNode.
* Reimplement by adding a `started` property to UnstartedMockNode.
* Throw IllegalStateException instead of NoSuchElementException.
* Add an isStarted property to UnstartedMockNode.
* In AbstractNode check if an initiating flow already has a flow registered to it and throw exception if one has been
In AbstractNode.internalRegisterFlowFactory check if a flow factory already exists for a initiating flow
If a factory does exist, throw an exception
A few tests needed to be fixed due to this change
* Reorder test setup to prevent flows from being registered multiple times
* Use check instead of if and throws statement in AbstractNode when checking for initiating flow having multiple flows mapped to it
Use check instead of if throws statement
Change names of methods in tests
Improve FlowRegistrationTest to better check if flow has been registered properly
* tidy up FlowFrameworkTests and FlowRegistrationTest
* Updated interoperability scenarios to use GA Release Candidate
* Removed "with proxy" and updated incorrect reference to OS master.
* Update to resolve Artifactory tools if available (blob-inspector, network-bootstrapper, database-migration)
* Allow passing in of argument to specify one or more scenarios to run.
* Updated to RC03.
* Added Oracle support in Behave framework and included functional test scenarios.
* behave test using snapshot (#970)
* make behave use snapshots from artifactory
* rebase and fix
* address PR issues
* address PR issues
* gradle task for bdd (#989)
* gradle task for bdd (#989)
* fix typo
* Publishing behave-api jar for use by external applications (eg. cordapp-option).
Fixed SIMMM valuation behave scenario test and startup.
* Publishing behave-api jar for use by external applications (eg. cordapp-option).
Fixed SIMMM valuation behave scenario test and startup.
* Various fixes to make BDD working in Teamcity (#1063)
* fix typo
* print docker log
* print docker log
* attempt to fix docker
* attempt to fix docker
* attempt to fix docker
* update to RC04
* disable clean up
* try to find out why the test pick up the wrong jar
* test
* minor fixes
* fix wrong bootstrapping procedure
* remove DISABLE_CLEANUP
* attempt to fix error
* fixes to get postgres working
* enable cleanup
* generate cucumber report
* bump to RC06
* attempt to make cucumber generate http report
* cucumber report
* some minor cleanup
* removed DP3 nodes from scenarios, added oracle and bumped to RC07
* fix licence issue
* fixed bootstrapper placing corda jar
* Update interoperability.feature
* Added missing published artifact.
* Fixed compilation errors raised by stricter compilation flag checking.
* Minor changes following rebase from master and re-testing.
* Updates to reflect last minute naming and versioning changes applied to 3.0 release.
Updated scenarios to use the officially released version of CE 3.0
* Updates following lastest PR review feedback.
* Updates following lastest PR review feedback.
* Align with master (maxMessageSize = mazTransactionSize).
* Fix snapshot version regex matching.
* Set logging level to DEBUG to ensure pattern matches catch log message output which has been downgraded from INFO
* Add all supported interoperable versions.
* Add jitter to flow retries
See https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/
* Add two seconds timeout to `timed flow is retried` test
* Minimum jittered delay is one second
* Adjust default retry config
Make sure the last retry fires after more than 20 minutes, which
is twice the default network map update. This way the notary should
have the latest network map when the last retry kicks in.
"app", "rpc", "p2p" and "unknown" have security implications (see isUploaderTrusted method) and thus they are not allowed to be used in the uploader field when importing attachments via the public API.
* There is a duplication of the kotlin introduce part, which is the same as the description of the "Note" section right below. So remove this duplicated part but keep the "Note".
* A miner change about the build node folder structure, first is Notary node doesn't need one web server, second is in V3.0, there are 5 windows totally but not 8.
* Miner updates for the format of changes, as instructed by Joel on https://github.com/corda/corda/pull/3012
* Add registerFlowFactory method to public test API
* Return CordaFuture rather than a plain Future
* Rename method
* Improve KDoc
* Hide internal interface with public wrapper
* Modify API current to include ResponderFlowFactory interface
* Take API definition change from generated file
* Note API change in changelog
* InMemoryMessagingNetwork.InMemoryMessaging renamed to MockNodeMessagingService and moved to internal package
* start method added to MockNodeMessagingService which enables AbstractNode to call makeMessagingService in its c'tor
* Removed TopicStringValidator as it's no longer used
* Clean up of TestStartedNode
* Merged InMemoryMessagingTests into InternalMockNetworkTests as it's testing InternalMockNetwork
Or else tests are going to fail on Windows, e.g.:
https://ci-master.corda.r3cev.com/viewLog.html?buildId=103027&tab=buildResultsDiv&buildTypeId=Corda_BuildWindowsTest
```
java.lang.IllegalArgumentException: Illegal character in path at index 95: file:/F:/buildAgent/work/f0cf2ea65c8f73ab/finance/build/libs/corda-finance-4.0-SNAPSHOT.jar/net\corda\finance\contracts\asset\BilateralNetState.class
at java.net.URI.create(URI.java:852)
at net.corda.testing.node.internal.JarEntryInfo$Companion.classFileURL(TestCordappsUtils.kt:209)
at net.corda.testing.node.internal.JarEntryInfo$Companion.access$classFileURL(TestCordappsUtils.kt:199)
at net.corda.testing.node.internal.JarEntryInfo$ClassJarEntryInfo.<init>(TestCordappsUtils.kt:178)
at net.corda.testing.node.internal.TestCordappsUtilsKt.jarEntryInfo(TestCordappsUtils.kt:56)
at net.corda.testing.node.internal.MutableTestCorDapp$Companion.jarEntriesFromClasses(MutableTestCorDapp.kt:42)
...
```
* ENT-2293: Skeleton of the new "rpcWorker" module
* ENT-2293: Add first failing test
(RPC server has not been implemented or started yet)
* ENT-2293: Further progress to start RPC server (unfinished)
* ENT-2293: RPC server started to work.
* ENT-2293: Slim down RpcWorker.
* ENT-2293: Minor changes.
* ENT-2293: Minor refactoring
* ENT-2293: Expand test coverage.
* ENT-2293: Introduce PicoCli for command line parsing.
* ENT-2293: Changes to make RPC server actually start.
* ENT-2293: Create simple RPC client.
* ENT-2293: Initialize serialization outside of RpcWorker.
* CORDA-1672 - Enable better user-helpful error messages
The issue is that the error reporting framework in the serializer is
targeted at developers in the node. However, because we pass exceptions
to users over RPC those error messages aren't always helpful.
Keep an internal exception that tracks debug useful information and log
that just before any exception escapes the framework and allow for
specific user "problem mitigation" issues to be set.
* wip
* update remaining excepions
* Explicitly add/update checkpoints rather than calling `addOrUpdate` which will run a `select` statement and then a add or update statement.
* Use `currentState.isAnyCheckpointPersisted()` to check for previous checkpoints
