From 99df70cd2eb8866c4e8ec2ef3c6e2f1e8ea9b2bd Mon Sep 17 00:00:00 2001 From: Nick Gaski Date: Wed, 9 Nov 2016 14:33:24 -0500 Subject: [PATCH] migration doc edits adjusted links to v0.6 branch fixed hyperlink to interfaces.go added new links [ci skip] Change-Id: I092e56adfd7cb0bf1dd905207164175cec59e641 Signed-off-by: Nick Gaski --- docs/v0.6_migration.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/v0.6_migration.md b/docs/v0.6_migration.md index 67492a82c5f..67d84205724 100644 --- a/docs/v0.6_migration.md +++ b/docs/v0.6_migration.md @@ -10,7 +10,7 @@ Hyperledger shim: The chaincode interface has changed from `shim.ChaincodeStub` to `shim.ChaincodeStubInterface`. See the -[interfaces.go](fabric/core/chaincode/shim/interfaces.go) file for the shim +[interfaces.go](https://github.com/hyperledger/fabric/blob/v0.6/core/chaincode/shim/interfaces.go) file for the shim source code. The following code snippet from line 74 of chaincode_example02 will highlight this alteration. @@ -115,7 +115,7 @@ to a client-side node application leveraging the hfc SDK. This is done by implementing the EventHub Service in your node program. The EventHub Service listens for events. -You can customize the eventsender.go code to determine which events you want +You can customize the [eventsender.go](https://github.com/hyperledger/fabric/blob/v0.6/examples/chaincode/go/eventsender/eventsender.go) code to determine which events you want sent. In the example, only the invoke transaction type is coded to send outgoing events. See the following code snippet in eventsender.go which demonstrates invocations being broadcast by the event sender: @@ -176,7 +176,7 @@ Explore the full library of the [sample event application](https://github.com/ra for the application source code and deeper documentation. __2.__ Java chaincode shim - new shim library to support java chaincode interacting -with Hyperledger fabric. See the [java shim](fabric/core/chaincode/shim/java) +with Hyperledger fabric. See the [java shim](https://github.com/hyperledger/fabric/tree/v0.6/core/chaincode/shim/java) library for the source code. __3.__ Ability to call chaincode using a 64encoded string. A custom UnmarshalJSON @@ -198,7 +198,7 @@ malfunctioning and/or non-deterministic chaincode and should be avoided: - Substituting global memory or cache storage for ledger state variables in the chaincode - Accessing external services (e.g. databases) directly from the chaincode - Using libraries or globabl variables that could introduce non-determinism (e.g. "random" or "time") -- For templates of deterministic and properly-written chaincode, see the [examples](fabric/examples/chaincode) library. This directory contains samples written in Go and Java. +- For templates of deterministic and properly-written chaincode, see the [examples](https://github.com/hyperledger/fabric/tree/v0.6/examples/chaincode) library. This directory contains samples written in Go and Java. __7.__ Fabric Starter Kit - This section describes how to set up a self-contained environment for application development with the Hyperledger fabric. The setup @@ -219,7 +219,7 @@ the blockchain service. __9.__ Fabric v0.6 provides the ability to dynamically register and enroll users with attributes through the hfc SDK. -See [asset-mgmt-with-dynamic-roles.js](fabric/sdk/node/test/unit/asset-mgmt-with-dynamic-roles.js) +See [asset-mgmt-with-dynamic-roles.js](https://github.com/hyperledger/fabric/blob/v0.6/sdk/node/test/unit/asset-mgmt-with-dynamic-roles.js) as an example. The hfc SDK previously allowed you to dynamically enroll users, but these users were already registered and aligned with attributes/affiliations hardcoded in the membersrvc.yml. Now a user with `registrar` authority can