mirror of
https://github.com/corda/corda.git
synced 2024-12-19 13:08:04 +00:00
Release and upgrade notes for V1.0 (#1736)
* Release and upgrade notes for V1.0 * Update changelog.rst * Update changelog.rst * Formatting. * Incorporating review feedback from KB and MN. * "guarantee" instead of "promise" * Updated with final review comments from KB and RGB. * Updated upgrade notes to describe migration from removed CordaPluginRegistry. * Minor clarification. * Minor updates following final RGB feedback. * Kat's further pedantic feedback * Minor changes following feedback from KB. * Incorporating review feedback from MH. * killed 'patent-pending'
This commit is contained in:
josecoll
GitHub
parent
e8fe1afff3
commit
059c330cae
@ -9,6 +9,8 @@ UNRELEASED
|
||||
|
||||
* ``Cordapp`` now has a name field for identifying CorDapps and all CorDapp names are printed to console at startup.
|
||||
|
||||
.. _changelog_v1:
|
||||
|
||||
Release 1.0
|
||||
-----------
|
||||
|
||||
@ -237,6 +239,8 @@ Release 1.0
|
||||
|
||||
* ``@RPCSinceVersion``, ``RPCException`` and ``PermissionException`` have moved to ``net.corda.client.rpc``.
|
||||
|
||||
.. _changelog_m14:
|
||||
|
||||
Milestone 14
|
||||
------------
|
||||
|
||||
@ -330,6 +334,8 @@ Milestone 14
|
||||
* Added JPA ``AbstractPartyConverter`` to ensure identity schema attributes are persisted securely according to type
|
||||
(well known party, resolvable anonymous party, completely anonymous party).
|
||||
|
||||
.. _changelog_m13:
|
||||
|
||||
Milestone 13
|
||||
------------
|
||||
|
||||
@ -409,8 +415,10 @@ support for more currencies to the DemoBench and Explorer tools.
|
||||
* Upgraded BouncyCastle to v1.57.
|
||||
* Upgraded Requery to v1.3.1.
|
||||
|
||||
Milestone 12
|
||||
------------
|
||||
.. _changelog_m12:
|
||||
|
||||
Milestone 12 (First Public Beta)
|
||||
--------------------------------
|
||||
|
||||
* Quite a few changes have been made to the flow API which should make things simpler when writing CorDapps:
|
||||
|
||||
|
||||
@ -5,17 +5,112 @@ Here are release notes for each snapshot release from M9 onwards.
|
||||
|
||||
Unreleased
|
||||
----------
|
||||
|
||||
Release 1.0
|
||||
-----------
|
||||
Corda 1.0 is finally here!
|
||||
|
||||
* Flow communications API has been redesigned around session based communication.
|
||||
This critical step in the Corda journey enables the developer community, clients, and partners to build on Corda with confidence.
|
||||
Corda 1.0 is the first released version to provide API stability for Corda application (CorDapp) developers.
|
||||
Corda applications will continue to work against this API with each subsequent release of Corda. The public API for Corda
|
||||
will only evolve to include new features.
|
||||
|
||||
* Merged handling of well known and confidential identities in the identity service.
|
||||
As of Corda 1.0, the following modules export public APIs for which we guarantee to maintain backwards compatibility,
|
||||
unless an incompatible change is required for security reasons:
|
||||
|
||||
* Remove `IssuerFlow` as it allowed nodes to request arbitrary amounts of cash to be issued from any remote node.
|
||||
* core
|
||||
Contains the bulk of the APIs to be used for building CorDapps: contracts, transactions, flows, identity, node services,
|
||||
cryptographic libraries, and general utility functions.
|
||||
|
||||
* Remove the legacy web front end from the SIMM demo. This was a very early sample, and does not reflect the quality of
|
||||
current Corda code. It may be replaced with a new front end based on a more recent version of AngularJS in a later release.
|
||||
* client-rpc
|
||||
An RPC client interface to Corda, for use by both UI facing clients and integration with external systems.
|
||||
|
||||
* client-jackson
|
||||
Utilities and serialisers for working with JSON representations of basic types.
|
||||
|
||||
Our extensive testing frameworks will continue to evolve alongside future Corda APIs. As part of our commitment to ease of use and modularity
|
||||
we have introduced a new test node driver module to encapsulate all test functionality in support of building standalone node integration
|
||||
tests using our DSL driver.
|
||||
|
||||
Please read :doc:`api-index` for complete details.
|
||||
|
||||
.. note:: it may be necessary to recompile applications against future versions of the API until we begin offering
|
||||
`ABI (Application Binary Interface) <https://en.wikipedia.org/wiki/Application_binary_interface>`_ stability as well.
|
||||
We plan to do this soon after this release of Corda.
|
||||
|
||||
Significant changes implemented in reaching Corda API stability include:
|
||||
|
||||
* **Flow framework**:
|
||||
The Flow framework communications API has been redesigned around session based communication with the introduction of a new
|
||||
``FlowSession`` to encapsulate the counterparty information associated with a flow.
|
||||
All shipped Corda flows have been upgraded to use the new `FlowSession`. Please read :doc:`api-flows` for complete details.
|
||||
|
||||
* **Complete API cleanup**:
|
||||
Across the board, all our public interfaces have been thoroughly revised and updated to ensure a productive and intuitive developer experience.
|
||||
Methods and flow naming conventions have been aligned with their semantic use to ease the understanding of CorDapps.
|
||||
In addition, we provide ever more powerful re-usable flows (such as `CollectSignaturesFlow`) to minimize the boiler-plate code developers need to write.
|
||||
|
||||
* **Simplified annotation driven scanning **:
|
||||
CorDapp configuration has been made simpler through the removal of explicit configuration items in favour of annotations
|
||||
and classpath scanning. As an example, we have now completely removed the `CordaPluginRegistry` configuration.
|
||||
Contract definitions are no longer required to explicitly define a legal contract reference hash. In their place an
|
||||
optional `LegalProseReference` annotation to specify a URI is used.
|
||||
|
||||
* **Java usability**:
|
||||
All code has been updated to enable simple access to static API parameters. Developers no longer need to
|
||||
call getter methods, and can reference static API variables directly.
|
||||
|
||||
In addition to API stability this release encompasses a number of major functional improvements, including:
|
||||
|
||||
* **Contract constraints**:
|
||||
Provides a means with which to enforce a specific implementation of a State's verify method during transaction verification.
|
||||
When loading an attachment via the attachment classloader, constraints of a transaction state are checked against the
|
||||
list of attachment hashes provided, and the attachment is rejected if the constraints are not matched.
|
||||
|
||||
* **Signature Metadata support**:
|
||||
Signers now have the ability to add metadata to their digital signatures. Whereas previously a user could only sign the Merkle root of a
|
||||
transaction, it is now possible for extra information to be attached to a signature, such as a platform version
|
||||
and the signature-scheme used.
|
||||
|
||||
.. image:: resources/signatureMetadata.png
|
||||
|
||||
* **Backwards compatibility and improvements to core transaction data structures**:
|
||||
A new Merkle tree model has been introduced that utilises sub-Merkle trees per component type. Components of the
|
||||
same type, such as inputs or commands, are grouped together and form their own Merkle tree. Then, the roots of
|
||||
each group are used as leaves in the top-level Merkle tree. This model enables backwards compatibility, in the
|
||||
sense that if new component types are added in the future, old clients will still be able to compute the Merkle root
|
||||
and relay transactions even if they cannot read (deserialise) the new component types. Due to the above,
|
||||
`FilterTransaction` has been made simpler with a structure closer to `WireTransaction`. This has the effect of making the API
|
||||
more user friendly and intuitive for both filtered and unfiltered transactions.
|
||||
|
||||
* **Enhanced component privacy**:
|
||||
Corda 1.0 is equipped with a scalable component visibility design based on the above sophisticated
|
||||
sub-tree model and the introduction of nonces per component. Roughly, an initial base-nonce, the "privacy-salt",
|
||||
is used to deterministically generate nonces based on the path of each component in the tree. Because each component
|
||||
is accompanied by a nonce, we protect against brute force attacks, even against low-entropy components. In addition,
|
||||
a new privacy feature is provided that allows non-validating notaries to ensure they see all inputs and if there was a
|
||||
`TimeWindow` in the original transaction. Due to the above, a malicious user cannot selectively hide one or more
|
||||
input states from the notary that would enable her to bypass the double-spending check. The aforementioned
|
||||
functionality could also be applied to Oracles so as to ensure all of the commands are visible to them.
|
||||
|
||||
.. image:: resources/subTreesPrivacy.png
|
||||
|
||||
* **Full support for confidential identities**:
|
||||
This includes rework and improvements to the identity service to handle both `well known` and `confidential` identities.
|
||||
This work ships in an experimental module in Corda 1.0, called `confidential-identities`. API stabilisation of confidential
|
||||
identities will occur as we make the integration of this privacy feature into applications even easier for developers.
|
||||
|
||||
* **Re-designed network map service**:
|
||||
The foundations for a completely redesigned network map service have been implemented to enable future increased network
|
||||
scalability and redundancy, support for multiple notaries, and administration of network compatibility zones and business networks.
|
||||
|
||||
Finally, please note that the 1.0 release has not yet been security audited.
|
||||
|
||||
We have provided a comprehensive :doc:`upgrade-notes` to ease the transition of migrating CorDapps to Corda 1.0
|
||||
|
||||
Upgrading to this release is strongly recommended, and you will be safe in the knowledge that core APIs will no longer break.
|
||||
|
||||
Thank you to all contributors for this release!
|
||||
|
||||
Milestone 14
|
||||
------------
|
||||
|
||||
@ -6,4 +6,6 @@ Release process
|
||||
|
||||
release-notes
|
||||
changelog
|
||||
upgrade-notes
|
||||
codestyle
|
||||
testing
|
||||
BIN
docs/source/resources/signatureMetadata.png
Normal file
BIN
docs/source/resources/signatureMetadata.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
docs/source/resources/subTreesPrivacy.png
Normal file
BIN
docs/source/resources/subTreesPrivacy.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 103 KiB |
@ -22,8 +22,8 @@ Classes get onto the whitelist via one of three mechanisms:
|
||||
#. Via the ``@CordaSerializable`` annotation. In order to whitelist a class, this annotation can be present on the
|
||||
class itself, on any of the super classes or on any interface implemented by the class or super classes or any
|
||||
interface extended by an interface implemented by the class or superclasses.
|
||||
#. By returning the class as part of a plugin via the method ``customizeSerialization``. It's important to return
|
||||
true from this method if you override it, otherwise the plugin will be excluded. See :doc:`writing-cordapps`.
|
||||
#. By implementing the ``SerializationWhitelist`` interface and specifying a list of `whitelist` classes.
|
||||
See :doc:`writing-cordapps`.
|
||||
#. Via the built in Corda whitelist (see the class ``DefaultWhitelist``). Whilst this is not user editable, it does list
|
||||
common JDK classes that have been whitelisted for your convenience.
|
||||
|
||||
|
||||
349
docs/source/upgrade-notes.rst
Normal file
349
docs/source/upgrade-notes.rst
Normal file
@ -0,0 +1,349 @@
|
||||
Upgrade notes
|
||||
=============
|
||||
|
||||
These notes provide helpful instructions to upgrade your Corda Applications (CorDapps) from previous versions, starting
|
||||
from our first public Beta (:ref:`Milestone 12 <changelog_m12>`), to :ref:`V1.0 <changelog_v1>`
|
||||
|
||||
General
|
||||
-------
|
||||
Always remember to update the version identifiers in your project gradle file:
|
||||
|
||||
.. sourcecode:: shell
|
||||
|
||||
ext.corda_release_version = '1.0.0'
|
||||
ext.corda_gradle_plugins_version = '1.0.0'
|
||||
|
||||
It may be necessary to update the version of major dependencies:
|
||||
|
||||
.. sourcecode:: shell
|
||||
|
||||
ext.kotlin_version = '1.1.4'
|
||||
ext.quasar_version = '0.7.9'
|
||||
|
||||
Please consult the relevant release notes of the release in question. If not specified, you may assume the
|
||||
versions you are currently using are still in force.
|
||||
|
||||
We also strongly recommend cross referencing with the :doc:`changelog` to confirm changes.
|
||||
|
||||
:ref:`Milestone 14 <changelog_m14>`
|
||||
------------
|
||||
|
||||
Build
|
||||
^^^^^
|
||||
|
||||
* MockNetwork has moved.
|
||||
|
||||
A new test driver module dependency needs to be including in your project: `corda-node-driver`. To continue using the
|
||||
mock network for testing, add the following entry to your gradle build file:
|
||||
|
||||
.. sourcecode:: shell
|
||||
|
||||
testCompile "net.corda:corda-node-driver:$corda_release_version"
|
||||
|
||||
.. note:: you may only need `testCompile "net.corda:corda-test-utils:$corda_release_version"` if not using the Driver DSL.
|
||||
|
||||
Configuration
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
* ``CordaPluginRegistry`` has been removed.
|
||||
The one remaining configuration item ``customizeSerialisation``, which defined a optional whitelist of types for use in
|
||||
object serialization, has been replaced with the ``SerializationWhitelist`` interface which should be implemented to
|
||||
define a list of equivalent whitelisted classes.
|
||||
You will need to rename your services resource file to the new class name:
|
||||
'resources/META-INF/services/net.corda.core.node.CordaPluginRegistry' becomes 'resources/META-INF/services/net.corda.core.serialization.SerializationWhitelist'
|
||||
An associated property on ``MockNode`` was renamed from ``testPluginRegistries`` to ``testSerializationWhitelists``.
|
||||
In general, the ``@CordaSerializable`` annotation is the preferred method for whitelisting as described in :doc:`serialization`
|
||||
|
||||
Missing imports
|
||||
^^^^^^^^^^^^^^^
|
||||
|
||||
Use the automatic imports feature of IntelliJ to intelligently resolve the new imports.
|
||||
|
||||
* Missing imports for contract types.
|
||||
|
||||
CommercialPaper and Cash are now contained within the `finance` module, as are associated helpers functions.
|
||||
For example:
|
||||
``import net.corda.contracts.ICommercialPaperState`` becomes ``import net.corda.finance.contracts.ICommercialPaperState``
|
||||
|
||||
``import net.corda.contracts.asset.sumCashBy`` becomes ``import net.corda.finance.utils.sumCashBy``
|
||||
|
||||
``import net.corda.core.contracts.DOLLARS`` becomes ``import net.corda.finance.DOLLARS``
|
||||
|
||||
``import net.corda.core.contracts.issued by`` becomes ``import net.corda.finance.issued by``
|
||||
|
||||
``import net.corda.contracts.asset.Cash`` becomes ``import net.corda.finance.contracts.asset.Cash``
|
||||
|
||||
* Missing imports for utility functions.
|
||||
|
||||
Many common types and helper methods have been consolidated into `net.corda.core.utilities` package.
|
||||
For example:
|
||||
``import net.corda.core.crypto.commonName`` becomes ``import net.corda.core.utilities.commonName``
|
||||
|
||||
``import net.corda.core.crypto.toBase58String`` becomes ``import net.corda.core.utilities.toBase58String``
|
||||
|
||||
``import net.corda.core.getOrThrow`` becomes ``import net.corda.core.utilities.getOrThrow``
|
||||
|
||||
* Missing flow imports.
|
||||
|
||||
In general all reusable library flows are contained within the **core** API `net.corda.core.flows` package.
|
||||
Financial domain library flows are contained within the **finance** module `net.corda.finance.flows` package.
|
||||
Other flows that have moved include:
|
||||
|
||||
``import net.corda.core.flows.ResolveTransactionsFlow`` becomes ``import net.corda.core.internal.ResolveTransactionsFlow``
|
||||
|
||||
Core data structures
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* Missing Contract override.
|
||||
|
||||
The contract interace attribute ``legalContractReference`` has been removed, and replaced by
|
||||
the optional annotation ``@LegalProseReference(uri = "<URI>")``
|
||||
|
||||
* Unresolved reference.
|
||||
|
||||
Calls to ``AuthenticatedObject`` are replaced by ``CommandWithParties``
|
||||
|
||||
* Overrides nothing: ``isRelevant`` in ``LinearState``.
|
||||
|
||||
Removed the concept of relevancy from ``LinearState``. A ``ContractState``'s relevance to the vault is now resolved
|
||||
internally; the vault will process any transaction from a flow which is not derived from transaction resolution verification.
|
||||
The notion of relevancy is subject to further improvements to enable a developer to control what state the vault thinks
|
||||
are relevant.
|
||||
|
||||
* Calls to ``txBuilder.toLedgerTransaction()`` now requires a serviceHub parameter.
|
||||
|
||||
Used by the new Contract Constraints functionality to validate and resolve attachments.
|
||||
|
||||
Flow framework
|
||||
^^^^^^^^^^^^^^
|
||||
|
||||
* Flow session deprecations
|
||||
|
||||
``FlowLogic`` communication has been upgraded to use functions on ``FlowSession`` as the base for communication
|
||||
between nodes.
|
||||
|
||||
* Calls to ``send()``, ``receive()`` and ``sendAndReceive()`` on FlowLogic should be replaced with calls
|
||||
to the function of the same name on ``FlowSession``. Note that the replacement functions do not take in a destination
|
||||
parameter, as this is defined in the session.
|
||||
|
||||
* Initiated flows now take in a ``FlowSession`` instead of ``Party`` in their constructor. If you need to access the
|
||||
counterparty identity, it is in the ``counterparty`` property of the flow session.
|
||||
|
||||
See ``FlowSession`` for step by step instructions on porting existing flows to use the new mechanism.
|
||||
|
||||
* ``FinalityFlow`` now returns a single ``SignedTransaction``, instead of a ``List<SignedTransaction>``
|
||||
|
||||
* ``TransactionKeyFlow`` renamed to ``SwapIdentitiesFlow``
|
||||
|
||||
Note that ``SwapIdentitiesFlow`` must be imported from the *confidential-identities** package ''net.corda.confidential''
|
||||
|
||||
Node services (ServiceHub)
|
||||
^^^^^^^^^^^^^^
|
||||
|
||||
* VaultQueryService: unresolved reference to `vaultQueryService`.
|
||||
|
||||
Replace all references to ``<services>.vaultQueryService`` with ``<services>.vaultService``.
|
||||
Previously there were two vault APIs. Now there is a single unified API with the same functions: ``VaultService``.
|
||||
|
||||
* ``serviceHub.myInfo.legalIdentity`` no longer exists; use the ``ourIdentity`` property of the flow instead.
|
||||
|
||||
``FlowLogic.ourIdentity`` has been introduced as a shortcut for retrieving our identity in a flow
|
||||
|
||||
* ``getAnyNotary`` is gone - use ``serviceHub.networkMapCache.notaryIdentities[0]`` instead
|
||||
|
||||
Note: ongoing work to support multiple notary identities is still in progress.
|
||||
|
||||
* ``ServiceHub.networkMapUpdates`` is replaced by ``ServiceHub.networkMapFeed``
|
||||
|
||||
* ``ServiceHub.partyFromX500Name`` is replaced by ``ServiceHub.wellKnownPartyFromX500Name``
|
||||
Note: A "well known" party is one that isn't anonymous and this change was motivated by the confidential identities work.
|
||||
|
||||
RPC Client
|
||||
^^^^^^^^^^
|
||||
|
||||
* Missing API methods on `CordaRPCOps` interface.
|
||||
|
||||
* Calls to ``verifiedTransactionsFeed()`` and ``verifiedTransactions()`` have been replaced with:
|
||||
``internalVerifiedTransactionsSnapshot()`` and ``internalVerifiedTransactionsFeed()`` respectively
|
||||
|
||||
This is in preparation for the planned integration of Intel SGX™, which will encrypt the transactions feed.
|
||||
Apps that use this API will not work on encrypted ledgers: you should probably be using the vault query API instead.
|
||||
|
||||
* Accessing the `networkMapCache` via ``services.nodeInfo().legalIdentities`` returns a list of identities.
|
||||
The first element in the list is the Party object referring to a node's single identity.
|
||||
|
||||
This is in preparation for allowing a node to host multiple separate identities in future.
|
||||
|
||||
Testing
|
||||
^^^^^^^
|
||||
|
||||
Please note that `Clauses` have been removed completely as of V1.0.
|
||||
We will be revisiting this capability in a future release.
|
||||
|
||||
* CorDapps must be explicitly registered in ``MockNetwork`` unit tests.
|
||||
|
||||
This is done by calling ``setCordappPackages``, an extension helper function in the ``net.corda.testing`` package,
|
||||
on the first line of your `@Before` method. This takes a variable number of `String` arguments which should be the
|
||||
package names of the CorDapps containing the contract verification code you wish to load.
|
||||
You should unset CorDapp packages in your `@After` method by using ``unsetCordappPackages()`` after `stopNodes()`.
|
||||
|
||||
* CorDapps must be explicitly registered in ``DriverDSL`` and ``RPCDriverDSL`` integration tests.
|
||||
|
||||
Similarly, you must also register package names of the CorDapps containing the contract verification code you wish to load
|
||||
using the ``extraCordappPackagesToScan: List<String>`` constructor parameter of the driver DSL.
|
||||
|
||||
Finance
|
||||
^^^^^^^
|
||||
|
||||
* `FungibleAsset` interface simplification.
|
||||
|
||||
The ``FungibleAsset`` interface has been made simpler. The ``Commands`` grouping interface
|
||||
that included the ``Move``, ``Issue`` and ``Exit`` interfaces have all been removed, while the ``move`` function has
|
||||
been renamed to ``withNewOwnerAndAmount`` to be consistent with the ``withNewOwner`` function of the ``OwnableState``.
|
||||
|
||||
The following errors may be reported:
|
||||
|
||||
* override nothing (FungibleAsset): `move`
|
||||
* not a subtype of overridden FungibleAsset: `withNewOwner`
|
||||
* no longer need to override `override val contractHash: SecureHash? = null`
|
||||
* need to override `override val contract: Class<out Contract>? = null`
|
||||
|
||||
|
||||
Miscellaneous
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
* ``args[0].parseNetworkHostAndPort()`` becomes ``NetworkHostAndPort.parse(args[0])``
|
||||
|
||||
* There is no longer a ``NodeInfo.advertisedServices`` property.
|
||||
|
||||
The concept of advertised services has been removed from Corda. This is because it was vaguely defined and real world
|
||||
apps would not typically select random, unknown counterparties from the network map based on self-declared capabilities.
|
||||
We will introduce a replacement for this functionality, business networks, in a future release.
|
||||
|
||||
Gotchas
|
||||
^^^^^^^
|
||||
|
||||
* Beware to use the correct identity when issuing cash:
|
||||
|
||||
The 3rd parameter to ``CashIssueFlow`` should be the ** notary ** (not the ** node identity **)
|
||||
|
||||
|
||||
:ref:`Milestone 13 <changelog_m13>`
|
||||
------------
|
||||
|
||||
Core data structures
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* `TransactionBuilder` changes.
|
||||
|
||||
Use convenience class ``StateAndContract`` instead of ``TransactionBuilder.withItems()`` for passing
|
||||
around a state and its contract.
|
||||
|
||||
* Transaction building DSL changes:
|
||||
|
||||
* now need to explicitly pass the ContractClassName into all inputs and outputs.
|
||||
* `ContractClassName` refers to the class containing the “verifier” method.
|
||||
|
||||
* Contract verify method signature change.
|
||||
|
||||
``override fun verify(tx: TransactionForContract)`` becomes ``override fun verify(tx: LedgerTransaction)``
|
||||
|
||||
* No longer need to override Contract ``contract()`` function.
|
||||
|
||||
Node services (ServiceHub)
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
* ServiceHub API method changes.
|
||||
|
||||
``services.networkMapUpdates().justSnapshot`` becomes ``services.networkMapSnapshot()``
|
||||
|
||||
Configuration
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
* No longer need to define ``CordaPluginRegistry`` and configure ``requiredSchemas``
|
||||
|
||||
Custom contract schemas are automatically detected at startup time by class path scanning.
|
||||
For testing purposes, use the ``SchemaService`` method to register new custom schemas:
|
||||
eg. ``services.schemaService.registerCustomSchemas(setOf(YoSchemaV1))``
|
||||
|
||||
Identity
|
||||
^^^^^^^^
|
||||
|
||||
* Party names are now ``CordaX500Name``, not ``X500Name``
|
||||
|
||||
``CordaX500Name`` specifies a predefined set of mandatory (organisation, locality, country)
|
||||
and optional fields (commonName, organisationUnit, state) with validation checking.
|
||||
Use new builder CordaX500Name.build(X500Name(target)) or, preferably, explicitly define X500Name parameters using
|
||||
``CordaX500Name`` constructor.
|
||||
|
||||
Testing
|
||||
^^^^^^^
|
||||
|
||||
* MockNetwork Testing.
|
||||
|
||||
Mock nodes in node tests are now of type ``StartedNode<MockNode>``, rather than ``MockNode``
|
||||
MockNetwork now returns a BasketOf(<StartedNode<MockNode>>)
|
||||
Must call internals on StartedNode to get MockNode:
|
||||
a = nodes.partyNodes[0].internals
|
||||
b = nodes.partyNodes[1].internals
|
||||
|
||||
* Host and Port change.
|
||||
|
||||
Use string helper function ``parseNetworkHostAndPort()`` to parse a URL on startup.
|
||||
eg. ``val hostAndPort = args[0].parseNetworkHostAndPort()``
|
||||
|
||||
* The node driver parameters for starting a node have been reordered, and the node’s name needs to be given as an
|
||||
``CordaX500Name``, instead of using ``getX509Name``
|
||||
|
||||
|
||||
:ref:`Milestone 12 <changelog_m12>` (First Public Beta)
|
||||
-----------------------------------
|
||||
|
||||
Core data structures
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
* Transaction building
|
||||
|
||||
You no longer need to specify the type of a ``TransactionBuilder`` as ``TransactionType.General``
|
||||
``TransactionType.General.Builder(notary)`` becomes ``TransactionBuilder(notary)``
|
||||
|
||||
Build
|
||||
^^^^^
|
||||
|
||||
* Gradle dependency reference changes.
|
||||
|
||||
Module name has changed to include `corda` in the artifacts jar name:
|
||||
|
||||
.. sourcecode:: shell
|
||||
|
||||
compile "net.corda:core:$corda_release_version" -> compile "net.corda:corda-core:$corda_release_version"
|
||||
compile "net.corda:finance:$corda_release_version" -> compile "net.corda:corda-finance:$corda_release_version"
|
||||
compile "net.corda:jackson:$corda_release_version" -> compile "net.corda:corda-jackson:$corda_release_version"
|
||||
compile "net.corda:node:$corda_release_version" -> compile "net.corda:corda-node:$corda_release_version"
|
||||
compile "net.corda:rpc:$corda_release_version" -> compile "net.corda:corda-rpc:$corda_release_version"
|
||||
|
||||
Node services (ServiceHub)
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
* ServiceHub API changes.
|
||||
|
||||
``services.networkMapUpdates()`` becomes ``services.networkMapFeed()``
|
||||
``services.getCashBalances()`` becomes a helper method within the **finance** module contracts package: ``net.corda.finance.contracts.getCashBalances``
|
||||
|
||||
Finance
|
||||
^^^^^^^
|
||||
|
||||
* Financial asset contracts (Cash, CommercialPaper, Obligations) are now a standalone CorDapp within the **finance** module.
|
||||
|
||||
Need to import from respective package within `finance` module:
|
||||
eg. ``net.corda.finance.contracts.asset.Cash``
|
||||
|
||||
Likewise, need to import associated asset flows from respective package within `finance` module:
|
||||
eg. ``net.corda.finance.flows.CashIssueFlow``
|
||||
``net.corda.finance.flows.CashIssueAndPaymentFlow``
|
||||
``net.corda.finance.flows.CashExitFlow``
|
||||
|
||||
* Moved ``finance`` gradle project files into a ``net.corda.finance`` package namespace.
|
||||
|
||||
This may require adjusting imports of Cash flow references and also of ``StartFlow`` permission in ``gradle.build`` files.
|
||||
Associated flows (`Cash*Flow`, `TwoPartyTradeFlow`, `TwoPartyDealFlow`) must now be imported from this package.
|
||||
Loading…
Reference in New Issue
Block a user