mirror of
https://github.com/corda/corda.git
synced 2024-12-28 00:38:55 +00:00
30a829adbf
* Move CompositeSignaturesWithKeys into net.corda.core.crypto package. (cherry picked from commit 8f29562) * Rename and move CordaPluginRegistry to reflect its real purpose now. Simplify serialization code a bit. (cherry picked from commit e2ecd3a) * Docs: docsite improvements * Remove discussion of webserver from 'writing a cordapp' page. * Fixup some flow docs. * Add a couple more package descriptions. (cherry picked from commit 2aedc43) * Review comments (cherry picked from commit ba1d007) * Review comments - always apply default whitelist and no longer load it via ServiceLoader (cherry picked from commit 7d4d7bb) * Added wording about renaming services resource file
109 lines
4.3 KiB
Markdown
109 lines
4.3 KiB
Markdown
# Package net.corda.client.jackson
|
|
|
|
Utilities and serialisers for working with JSON representations of basic types. This adds Jackson support for
|
|
the java.time API, some core types, and Kotlin data classes.
|
|
|
|
# Package net.corda.client.jfx.model
|
|
|
|
Data models for binding data feeds from Corda nodes into a JavaFX user interface, by presenting the data as [javafx.beans.Observable]
|
|
types.
|
|
|
|
# Package net.corda.client.jfx.utils
|
|
|
|
Utility classes (i.e. data classes) used by the Corda JavaFX client.
|
|
|
|
# Package net.corda.client.mock
|
|
|
|
Tools used by the client to produce mock data for testing purposes.
|
|
|
|
# Package net.corda.client.rpc
|
|
|
|
RPC client interface to Corda, for use both by user-facing client and integration with external systems.
|
|
|
|
# Package net.corda.client.rpc.internal
|
|
|
|
Internal, do not use. These APIs and implementations which are currently being revised and are subject to future change.
|
|
|
|
# Package net.corda.core
|
|
|
|
Exception types and some utilities for working with observables and futures.
|
|
|
|
# Package net.corda.core.concurrent
|
|
|
|
Provides a simplified [java.util.concurrent.Future] class that allows registration of a callback to execute when the future
|
|
is complete.
|
|
|
|
# Package net.corda.core.contracts
|
|
|
|
This package contains the base data types for smarts contracts implemented in Corda. To implement a new contract start
|
|
with [Contract], or see the examples in [net.corda.finance.contracts].
|
|
|
|
Corda smart contracts are a combination of state held on the distributed ledger, and verification logic which defines
|
|
which transformations of state are valid.
|
|
|
|
# Package net.corda.core.cordapp
|
|
|
|
Classes that represent metadata about an app.
|
|
|
|
# Package net.corda.core.crypto
|
|
|
|
Cryptography data and utility classes used for signing, verifying, key management and data integrity checks.
|
|
|
|
# Package net.corda.core.flows
|
|
|
|
Base data types and abstract classes for implementing Corda flows. To implement a new flow start with [FlowLogic], or
|
|
see [CollectSignaturesFlow] for a simple example flow. Flows are started via a node's [ServiceHub].
|
|
|
|
Corda flows are a tool for modelling the interactions between two or more nodes as they negotiate a workflow.
|
|
This can range from a simple case of completing a trade which has been agreed upon externally, to more complex
|
|
processes such as handling fixing of interest rate swaps.
|
|
|
|
# Package net.corda.core.identity
|
|
|
|
Data classes which model different forms of identity (potentially with supporting evidence) for legal entities and services.
|
|
|
|
# Package net.corda.core.messaging
|
|
|
|
Data types used by the Corda messaging layer to manage state of messaging and sessions between nodes.
|
|
|
|
# Package net.corda.core.node.services
|
|
|
|
Services which run within a Corda node and provide various pieces of functionality such as identity management, transaction storage, etc.
|
|
|
|
# Package net.corda.core.node.services.vault
|
|
|
|
Supporting data types for the vault services.
|
|
|
|
# Package net.corda.core.schemas
|
|
|
|
Data types representing database schemas for storing Corda data via an object mapper such as Hibernate. Modifying Corda
|
|
state in the database directly is not a supported approach, however these can be used to read state for integrations with
|
|
external systems.
|
|
|
|
# Package net.corda.core.serialization
|
|
|
|
Supporting data types and classes for serialization of Corda data types.
|
|
|
|
# Package net.corda.core.transactions
|
|
|
|
Base data types for transactions which modify contract state on the distributed ledger.
|
|
|
|
The core transaction on the ledger is [WireTransaction], which is constructed by [TransactionBuilder]. Once signed a transaction is stored
|
|
in [SignedTransaction] which encapsulates [WireTransaction]. Finally there is a special-case [LedgerTransaction] which is used by contracts
|
|
validating transactions, and is built from the wire transaction by resolving all references into their underlying data (i.e. inputs are
|
|
actual states rather than state references).
|
|
|
|
# Package net.corda.core.utilities
|
|
|
|
Corda utility classes, providing a broad range of functionality to help implement both Corda nodes and CorDapps.
|
|
|
|
# Package net.corda.finance
|
|
|
|
The finance module is a CorDapp containing sample cash and obligation contracts, as well as providing several
|
|
useful data types such as [Amount].
|
|
|
|
# Package net.corda.finance.utils
|
|
|
|
A collection of utilities for summing financial states, for example, summing obligations to get total debts.
|
|
|