* Updated the performance cordapp tests to use target version 3 as it's not been updated and uses the old FinalityFlow API
* Updated the api-current.txt file as the API checker on TC is throwing a false-negative
* Deleted IntegrationTestingTutorial, rather than fixing its failure, as it's a leftover of KotlinIntegrationTestingTutorial
FinalityHandler is insecure in that it is open to receive any transaction from any party.
Any CorDapp targeting platform version 4 or above is required use the new c'tors which take in FlowSession objects to the counterpart flow. This flow must subcall ReceiveFinalityFlow to receive and record the finalised transaction.
Old CorDapps (with target platform version < 4) will continue to work as previously. However if there are no old CorDapps loaded then the node will disable FinalityHandler.
* ENT-2689: Intent of the changes to be made (doesn't compile)
* ENT-2689: Propagate renaming of `customSSLConfiguration`
* ENT-2689: Documentation update
* ENT-2689: More renaming
* ENT-2689: Add a test for SSL keystores location override
* ENT-2689: Add V3 configuration compatibility unit tests (failing for now)
* ENT-2689: Add ability to read V3 configs.
* ENT-2689: Reflect changes on Integration tests.
* ENT-2689: For BridgeControlListener use Artemis SSL configuration if specified, otherwise fall back onto main SSL configuration.
* Revert: ENT-2689: For BridgeControlListener use Artemis SSL configuration if specified, otherwise fall back onto main SSL configuration.
And rename `p2pSslOptions` to `publicSSLConfiguration`.
* ENT-2689: Move V3 config structures into a separate file.
* First pass
* Update test.
* Address review comments.
* Added docs and kdocs.
* Clean-up.
* Add extra test.
* Changes to docsite.
* Added try/catch block as recommended by Andras.
* Removed try catch block. It's not required as the checkpoint serialiser deals with this.
* Re-used existing DB session instead of creating a new session.
* Entity manager auto flushes.
* Added java friendly api.
* Addressed review comments.
* Minimum platform version checking for new signature constraints feature.
* Fix broken JUnit
* NP safety checking on network parameters.
* Warning and auto-downgrade of signed states that do not meet the minimum network platform version.
* ENT-2669: Introduce option for HTTP proxy for outbound Bridge connectivity
One of our customers currently using HTTP proxy without which outbound connection from Corda Node cannot be established.
Also, propagate `trace` setting correctly down the Bridge stack.
* ENT-2669: Compilation fixes.
* ENT-2669: Revert deleted constructor back.
* ENT-2669: First stub on HTTP Proxy integration test.
* ENT-2669: Minor changes.
* ENT-2669: Reduce test to bare minimum.
* ENT-2669: Attempt to write own HttpProxy.
* ENT-2669: Another attempt to make programmatic HttpProxy work.
* ENT-2697: Disable DNS resolution before sending requests to proxies.
* ENT-2669: Switch to use Jetty HttpProxy for integration testing.
* Adds a pipeline logger ahead of the proxy stage if trace is set. The logging is removed once the proxy completes.
Define a constant for pipeline stage.
* Introduce public subset of config to tweak config via mock net work without exposing internal node config.
* Removal of functions exposing (internal) NodeConfiguration from the public test API
* Code review fixes
* Blank lines removed
* Documented mock network API change in upgrade notes.
* Updated documentation and API doc.
* More documentation/API doc
* ENT-2669: Rename SocksProxyVersion into ProxyVersion
* ENT-2669: Rename SocksProxyConfig into ProxyConfig
Update documentation and make code changes such that old style configs are still parsed.
* ENT-2669: Changelog update
Note about database considerations regarding Cordapp compatibility between OS and ENT.
Remove database configuration "schema" as this is not implemented in OS, it was already mentioned as ignored for SQL server.
Database documentation updates:
Unused tables or ones related to network-services were removed from scripts in docs.
Added quota/tablespace when creating users in Oracle - as reported in https://r3-cev.atlassian.net/browse/ENT-2580 UNLIMITED is not required.
List all tables for granting permissions when setting read only user in Oracle and fix typo
Fix typo for SQL Server.
Improve example of vendor specific DDL requirements.
