f8ad5c9d10
* Vault Query Service API implementation using JPA Hibernate Added queryBy(QueryCriteria) Vault API and Junit tests. Minor cosmetic API changes following rebase. Fixes following rebase from master Upgraded to requery 1.3.1 WIP - removed 'latestOnly' from LinearStateQueryCriteria WIP - CommercialSchemas V2, V3, V4 testing WIP - sort out generics handling. WIP - most general queries completed. WIP - join queries, contractStateType derivation WIP - refactoring Requery WIP - refactored VaultService to extract a VaultQueryService interface (and associated Requery implementation). WIP - HibernateVaultQuery implementation WIP - Re-structured all Schema definitions (requery/jpa) and make Hibernate Config reusable. WIP - Multi-version schema testing, hibernate query testing. WIP - Custom Criteria and Fungible Criteria impl & testing. WIP - Kotlin Comparable Generics error WIP - Party queries all working now WIP - All VaultQueryTests now working (refactored for AND / OR composition) WIP - added schema registration in CordaPluginRegistry to enable custom vault queries on arbitrary schemas. WIP - added new default Sort NULL order to be NONE + added lots more tests for Logical Operator testing. Mostly identity fixes following rebase from master. Exception handling and public API cleanup in prep for PR. Additional tests for Logical Operators; additional tests for NULLS sort ordering; additional logging; Additional parser to handle Nullable attribute values; added Unary and Collection logical expression handlers Lots of cleanup: participants; trackBy interfaces; additional fungible tests; parser cleanup and improved support for Java Removed all traces of Requery implementation. Further minor cleanup and Junit test fix. Final identity and schema related identity clean-up. Revert unrelated changes. PR review updates: blank lines, isRelevant. Fixed wiring of updatesPublisher for dynamic trackBy queries. PR review changes: multi-versioned schema samples and associated dummy contracts moved to test packages. Fixed problem with sorted queries (not specifying any filterable criteria). PR review: minor updates to address RP comments. Typesafe custom query criteria Cleanup: remove redundant tests. Further clean-up and make all Java test work successfully. Remove debugging print statements. Rebased from master - changes required due to DealState module change. fixed broken assertion caused by DealState ordering change (different package) Fixed transaction demarcation issue causing "java.lang.IllegalStateException: Was not expecting to find existing database transaction on current strand" trackBy() now filters on ContractType and StateStatus (CONSUMED, UNCONSUMED, ALL) Added tests to exercise RPCOps trackBy and queryBy (RPC smoke test and CordaRPCOps) Added additional @CordaSerializable annotations. Updated documentation and referenced sample code. Added deprecation annotations. Re-added missing deprecation annotation. Hibernate debug logging is now configurable and disabled by default. Introduced common Sort attributes based on the node schemas. Completely removed NULL_HANDLING sort parameter as this is not supported in JPA. Revisited and fixed usage of @CordaSerializable. * Minor fix following rebase from master. * Remove blank line as per RP PR feedback request. * Minor Java documentation and example clean-up. * Disable BFT Notary Service tests. |
||
|---|---|---|
| .idea | ||
| buildSrc | ||
| client | ||
| config | ||
| cordform-common | ||
| core | ||
| docs | ||
| experimental | ||
| finance | ||
| gradle/wrapper | ||
| gradle-plugins | ||
| lib | ||
| node | ||
| node-api | ||
| node-schemas | ||
| samples | ||
| smoke-test-utils | ||
| test-utils | ||
| tools | ||
| verifier | ||
| webserver | ||
| .gitignore | ||
| build.gradle | ||
| constants.properties | ||
| CONTRIBUTING.md | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE | ||
| README.md | ||
| settings.gradle | ||
| TRADEMARK | ||
Corda
Corda is a decentralised database system in which nodes trust each other as little as possible.
Features
- A P2P network of nodes
- Smart contracts
- Flow framework
- "Notary" infrastructure to validate uniqueness of transactions
- Written as a platform for distributed apps called CorDapps
- Written in Kotlin, targeting the JVM
Getting started
Firstly, read the Getting started documentation.
Next, use the following guides to set up your dev environment:
-
If you are on Windows use this getting started guide which also explains through how to run the sample apps.
-
Alternatively if you are on Mac/Linux, watch this brief Webinar which walks through getting Corda, installing it, building it, running nodes and opening projects in IntelliJ.
After the above, watching the following webinars will give you a great introduction to Corda:
Webinar 1 – Introduction to Corda
Richard Brown, R3 Chief Technology Officer, explains Corda's unique architecture, the only distributed ledger platform designed by and for the financial industry's unique requirements. You may want to read the Corda non-technical whitepaper as pre-reading for this session.
Webinar 2 – Corda Developers’ Tutorial
Roger Willis, R3 Developer Relations Lead, provides an overview of Corda from a developer’s perspective and guidance on how to start building CorDapps. You may want to view Webinar 1 - Introduction to Corda as preparation for this session. NB. This was recorded for the M5 release.
Building on Corda
To build your own CorDapps:
- Clone the CorDapp Template repository
- Read the README (IMPORTANT!)
- Read the Writing a CorDapp documentation
To look at the Corda source and run some sample applications:
- Clone this repository
- To run some sample CorDapps, read the running the demos documentation
- Start hacking and contribute!
Useful links
Development State
Corda is under active development and is maturing rapidly. We are targeting production-readiness in 2017. The API will continue to evolve throughout 2017; backwards compatibility not assured until version 1.0.
Pull requests, experiments, and contributions are encouraged and welcomed.
Background
The project is supported by R3, a financial industry consortium, which is why it contains some code for financial use cases and why the documentation focuses on finance. The goal is to use it to construct a global ledger, simplifying finance and reducing the overheads of banking. But it is run as an open source project and the basic technology of a peer-to-peer decentralised database may be useful for many different projects.
Contributing
Please read here.
License
Acknowledgements
YourKit supports open source projects with its full-featured Java Profiler.
YourKit, LLC is the creator of YourKit Java Profiler and YourKit .NET Profiler, innovative and intelligent tools for profiling Java and .NET applications.