MockServices

<init>

Create a mock ServiceHub that looks for app code in the given package names, uses the provided identity service (you can get one from makeTestIdentityService) and represents the given identity.

Create a mock ServiceHub that can't load CorDapp code, which uses the provided identity service (you can get one from makeTestIdentityService) and which represents the given identity.

Create a mock ServiceHub that can't load CorDapp code, and which uses a default service identity.

Create a mock ServiceHub which uses the package of the caller to find CorDapp code. It uses the provided identity service (you can get one from makeTestIdentityService) and which represents the given identity.

Create a mock ServiceHub which uses the package of the caller to find CorDapp code. It uses the provided identity service (you can get one from makeTestIdentityService) and which represents the given identity. It has no keys.

A helper constructor that requires at least one test identity to be registered, and which takes the package of the caller as the package in which to find app code. This is the most convenient constructor and the one that is normally worth using. The first identity is the identity of this service hub, the rest are identities that it is aware of.

Create a mock ServiceHub which uses the package of the caller to find CorDapp code. It uses a default service identity.

attachments

Provides access to storage of arbitrary JAR files (which may contain only data, no code).

clock

A Clock representing the node's current time. This should be used in preference to directly accessing the clock so the current time can be controlled during unit testing.

contractUpgradeService

The ContractUpgradeService is responsible for securely upgrading contract state objects according to a specified and mutually agreed (amongst participants) contract version.

cordappClassloader

Returns the classloader containing all jar deployed in the 'cordapps' folder.

cordappProvider

Provides access to anything relating to cordapps including contract attachment resolution and app context

diagnosticsService

The DiagnosticsService provides diagnostic level information about the node, including the current version of the node, and the CorDapps currently installed on the node. Note that this information should be used to provide diagnostics only, and no functional decisions should be made based on this.

identityService

An identity service maintains a directory of parties by their associated distinguished name/public keys and thus supports lookup of a party given its key, or name. The service also manages the certificates linking confidential identities back to the well known identity (i.e. the identity in the network map) of a party.

keyManagementService

The key management service is responsible for storing and using private keys to sign things. An implementation of this may, for example, call out to a hardware security module that enforces various auditing and frequency-of-use requirements.

myInfo

The NodeInfo object corresponding to our own entry in the network map.

networkMapCache

A network map contains lists of nodes on the network along with information about their identity keys, services they provide and host names or IP addresses where they can be connected to. The cache wraps around a map fetched from an authoritative service, and adds easy lookup of the data stored within it. Generally it would be initialised with a specified network map service, which it fetches data from and then subscribes to updates of.

networkParameters

Returns the network parameters the node is operating under.

networkParametersService

Provides access to historical network parameters that are used in transaction resolution.

servicesForResolution

validatedTransactions

A map of hash->tx where tx has been signature/contract validated and the states are known to be correct. The signatures aren't technically needed after that point, but we keep them around so that we can relay the transaction data to other nodes that need it.

vaultService

The vault service lets you observe, soft lock and add notes to states that involve you or are relevant to your node in some way. Additionally you may query and track states that correspond to various criteria.

addMockCordapp

Add the given package name to the list of packages which will be scanned for cordapp contract verification code

cordaService

Return the singleton instance of the given Corda service type. This is a class that is annotated with CordaService and will have automatically been registered by the node.

jdbcSession

Exposes a JDBC connection (session) object using the currently configured database. Applications can use this to execute arbitrary SQL queries (native, direct, prepared, callable) against its Node database tables (including custom contract tables defined by extending net.corda.core.schemas.QueryableState).

loadContractAttachment

Returns a dummy Attachment, in context of signature constrains non-downgrade rule this default to contract class version 1.

loadState

Given a StateRef loads the referenced transaction and looks up the specified output ContractState.

loadStates

Given a Set of StateRef's loads the referenced transaction and looks up the specified output ContractState.

recordTransactions

Stores the given SignedTransactions in the local transaction storage and then sends them to the vault for further processing if statesToRecord is not StatesToRecord.NONE. This is expected to be run within a database transaction.

registerUnloadHandler

Allows the registration of a callback that may inform services when the app is shutting down.

withEntityManager

Exposes the Java Persistence API (JPA) to flows via a restricted EntityManager. This method can be used to persist and query entities which inherit from MappedSchema. This is particularly useful if off-ledger data needs to be kept in conjunction with on-ledger state data.

makeTestDatabaseAndMockServices

Makes database and mock services appropriate for unit tests.

makeTestDatabaseAndPersistentServices

Makes database and persistent services appropriate for unit tests which require persistence across the vault, identity service and key managment service.

makeTestDataSourceProperties

Make properties appropriate for creating a DataSource for unit tests.

getCashBalance

getCashBalances

ledger

Creates and tests a ledger built by the passed in dsl.

transaction

Creates a ledger with a single transaction, built by the passed in dsl.