* RELEASE: initial changes to release docs
* wip
* wip
* Upgrade notes for a table name change. (#3566)
Document table change name from v3.0 to v3.2, change introduced in v3.1 but not mentioned in v3.1 upgrade notes, back-port of PR #3567.
* wip
* wip
* wip
* CORDA-1812 - upgrade notes (#3618)
* CORDA-1812 upgrade notes
* CORDA-1812 upgrade notes
* CORDA-1804 - upgrade notes for CORDA-1804 (#3619)
* Missing upgrade notes for table change in v3.1 - related to CORDA-1804 (#3567)
Document different upgrade notes for table name change from v3.0 or from v3.1/v3.2 to the current version (a table change introduced in v3.1 was not documented in upgrade notes).
(cherry picked from commit 9f905da036)
* Move different table name upgrade paths under one section.
* Addressing PR comments.
* Addressing PR comments.
* review comments
* WIP
* WIP
* WIP
* Doc for bootstrapper (#3638)
* network-builder-docs
* docs for network-builder
* wip@
* final comments
* Hibernate session flushed before handing over raw JDBC session to user code + test - inserting and selecting cash in the same transaction
* Additional two tests copied from Enterprise repo
(cherry picked from commit ed70fea3a7)
* CORDA-1790 Roll back flow transaction on exception
* CORDA-1790 Roll back flow transaction on exception
* CORDA-1790 Roll back flow transaction on exception
* Fix a typo in node_attchments_contracts table name. (#3202)
(cherry picked from commit 57d379597b)
* CORDA-1804 Corda node stops when detecting not migrated node_attachments_contracts table name (#3593)
Database table NODE_ATTACHMENTS_CONTRACT_CLASS_NAME in v3.0 was changed to NODE_ATTCHMENTS_CONTRACTS in v3.1 and then finally NODE_ATTACHMENTS_CONTRACTS on current master. Users may omit the upgrade note and run into errors. After the change the node will not start if the new table name is not found and any other older ones is found.
(cherry picked from commit 208ac49da0)
* Fixes after cherry-pick of 208ac49da0.
* Cleanup and improvements to the serialisation format of JacksonSupport (needed for CORDA-1238) (#3102)
Also deprecated all the public members that shouldn't have leaked into the public API.
(cherry picked from commit 3bb95c3)
* CORDA-1238: Updated JacksonSupport to support SerializedBytes, CertPath, X509Certificate and the signature classes (#3145)
SerializedBytes are first converted to the object it represents before being serialised as a pojo.
These changes will be needed to support the the blob inspector when it will output to YAML/JSON.
(cherry picked from commit b031e66)
* Cherry picked part of commit 824adca to port over *only* the JackSupport refactoring.
* CORDA-1238: Moved the blob inspector out of experimental and wired it to JackonSupport (#3224)
The existing output format was not complete and so was deleted to avoid it becoming a tech debt. We can always resurrect it at a later point.
(cherry picked from commit 4e0378d)
* Added back support for parsing OpaqueBytes as UTF-8 strings in JacksonSupport (#3240)
(cherry picked from commit d772bc8)
* Cleaned up blob inspector doc (#3284)
(cherry picked from commit b7fbebb)
* Blobinspector: trace level logging with --verbose (#3313)
(cherry picked from commit 6a2e50b)
* Cherry picked part of commit 3046843 to fix issue with --version
* Fixes to the api file
Implement removal of stale nodes from network - backport (#3128)
Implement removal of stale nodes from network
Add eventHorizon to network parameters structure. Add republishing of
node info on 1 day intervals - it is treated by network map as heartbeat from node indicating if it's alive or not. Add removal of old node infos on network map signing.
Add copy method to network parameters data class
Add JvmOverloads annotation to the constructor, because it's data class
exposed in API
make NetworkParameters serialization compatible (#3234)
Cope with API checker inlining annotations
* CORDA-1510 - Allow Doorman and NetworkMap to be configured independently (#3220)
* CORDA-1510 - Allow Doorman and NetworkMap to be configured independently
Currently only one compatabilityZoneURL can be specified, however the
two services can be run on as separate servers. Allow nodes to be
configured in this manner
* Partial review comments
* Review comments
* review comments
* Test fix
* spell fix
* CORDA-1530 - Generics break default evolver
When selecting an annotated constructor for evolving a type make sure
we treat generics in the same manner we did when serialized. Effectively
throw away the template information and treat lists as lists and maps
as maps
* REVERT - CORDA-1264 - Needs more thought prior to release
This reverts commit 33af80ac55.
Since this causes regressions in the way errors are propogated to
clients it seems best to not break or hold up 3.1 but revert this commit
and move on
* fix revert
* ENT-1668: Don't crash on node startup when network map is not available (#2887)
Fix ENT-1668
Don't crash on node startup when network map is not available
* Add changelog entry
* ENT-1564 - add additional uploader check to the HashConstraint (#2845)
(cherry picked from commit 1a1cd94)
* ENT-1564 changelog entry
* ENT-1564 ignored tests that were removed in master
Problem manifests now that the classpath scanner is used by the
serialisation framework in factory initialization to locate pluggable
serializers. The actual thrown error is
java.lang.RuntimeException: Unknown constant pool tag
Given this is a known issue and a fixed bug it makes sense to move the
version forward. Unfortunately at this time we cannot move beyond
2.12.3 as 2.12.4 and later versions (up to the latest 2.18.1) exhibit
some other error that needs investigating. Thus, move to the latest
version that is stable for our current set of use cases.
More information on the nature of the problem exhibited by moving beyond
2.12.3 can be found on the linked Jira (ENT-1665) as well as details on
reproducing the issue moving forward to 2.12.3 fixes.
* Api scanner backport and update of api-current.txt
* Updated api-current based on current state of release branch
* Update to most recent version of api scanner
* Fix a couple of issues with the merge and regenerate the api file with the most recent version of the scanner.
* Update changelog/release notes
