* 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
* DOC: AMQP upgrade notes in brief
* moving test upgrade notes from release notes to upgrade note
* add cordapp/cordformation notes
* Added section for network map changes
* Updated upgrade notes to reflect changes for SSL (#2569)
* Updated upgrade notes to reflect changes for SSL
* Removed some blank lines.
* AMQP Constructor / property mismatch upgrade note
* wip
* Note about feasible (but not recommended) tables that can be migrated from Corda 2.0 to 3.0, basic recipe how to do it.
* Database schema changes - optional partial vault migration described at the end of the paragraph, focus on the overall changes to tables.
* Review Comments
* Database schema changes - split Vault and finance module changes, reformatting, improve migration note.
* Database schema changes - addressing PR comments.
* Database schema changes - move changes to change log, migration to JIRA ticket.
* Finalise versions
* review comments
* CORDA-1171: Add notes on the notary error change
* set release version
Current logic in `CashWidget` is not handling well updates done in close succession, i.e. less than 1 second.
And such frequent updates do indeed happen, e.g. from: `net.corda.client.jfx.model.ContractStateModel#cashStates`
where `list` is modified twice.
Also use `.toDecimal()` instead of `.quantity`to have amount represented in pounds rather than in pennies.
