Currently only local deployment of Java chaincode is supported.

Change-Id: Id7651f6eeae232260f76f2280b935f7c9a15d169
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

This will fix issue FAB-215
https://jira.hyperledger.org/browse/FAB-215



Change-Id: I2599ba09f81ae44f9e6f28b53917300d2922a897
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

In docker-compose-1-empty.yml nc was being invoked directly which led
to SIGTERM being ignored by the container. This added an unneccessary
10 second wait after tests that used it while docker timed out and
sends a SIGKILL. This fixes that by forking nc and trapping SIGTERM
and directly killing nc.

Change-Id: Ifc5072b33c45f9fa90868a87ca69982c051e10e1
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

Current JDK image sourced from dockerhub (java:openjdk-8) is being
deprecated (see https://hub.docker.com/_/java/

). Update the relevent
docker file to use the new openjdk:8 image.

Change-Id: Idf9bac8ac6f981ea6e0311190365f37f98915666
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

The `peer network login` command does not specify that it
requires a username argument:

$ peer network login
Error: Must supply username
Usage:
  peer network login [flags]

This change modifies the usage message to:

Usage:
  peer network login <username> [flags]

Change-Id: I7ffbc312a9ee33ba34584c4cb57d091ffeb4b2dc
Signed-off-by: Bradley Gorman <bgorman@au1.ibm.com>

When attempting to deploy with the peer CLI, if the user has not
logged in they get the error "User x not logged in. Use the
'login' command to obtain a security token."

It took me a couple of minutes to figure out what the 'login'
command actually is. I feel the error should specify it as
'peer network login'.

I think this error is specific to the `peer` CLI code,
so it should not affect REST or the Node SDK.

Change-Id: I3d6d4e748d9dbf543c50c2754ef21cacfa14a069
Signed-off-by: Bradley Gorman <bgorman@au1.ibm.com>

The name of the field UUID was also changed to TxID.

Change-Id: Iedeed9af13a99671a756c32944a8c6814d4b2b20
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Change print() statements to bdd_log(), defined in bdd_test_util.py
This change provides a manner for keeping all log statements in the
same format. Currently this format is simply the current time
followed by the speicified message.

Also added the copyright header to sdk_impl.py and removed unused
imports.

Change-Id: I87590bbcd6512eefcce46dc9e7f854597c203b17
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

Remove deprecated devops API. Skipped one behave test that still used
it. Will open separate issue to deal with that. Update API docs.

Fixes FAB-258

rebased

Change-Id: Iba55fb271aca5a1d1d8e895ecc6ff34c69f59ac2
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

TestHTTPExecuteDeployTransaction is failing on master
because it is trying to go get
http://github.com/hyperledger/fabric-test-resources/examples/chaincode/go/chaincode_example01


which implements new interfaces from the convergence branch.
This patch points the test at a different repo for now and demonstrates usage of
gopkg.in to attempt to overcome limitations of go versioning

Fixes FAB-305

Change-Id: I55113b36a7cd6c505e7dc2503a31d91fa11b8c5b
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

Change-Id: I1b840d303674b7469d537aa3f70a87530f757b06
Signed-off-by: Srirama Sharma <sriramsh@in.ibm.com>

Before this change, the SDK aborted when adding a peer with
an invalid URL.  This change correctly handles the case when the URL
does not begin with 'grpc' or 'grpcs' and returns an 'InvalidProtocol'
error message

Fixes FAB-256

Change-Id: I7791acc49b4c9b05511155d399d882b884128c4c
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

Current node SDK will create a new member object if
it is not in cache and restore state from persistence,
but it does not add new member in cache.

Change-Id: Ifb7b17e8e40c1b4afe59acefa020eb3f0760ed59
Signed-off-by: grapebaba <281165273@qq.com>

I noticed a lot of the examples no longer compiled after the
recent changes to the chaincode Function and Args. To counter this
issue in future I would like to bring the examples into the normal
unit testing run.

I've excluded specific examples as they have various issues:

chaintool has issues with the GOPATH not containing its
dynamically built files.

go/asset_management* tests panic on some RocksDB calls.

go/rbac_tcerts_no_attrs has some sort of missing config.

go/utxo relies on bitcoin source.

Change-Id: Ibfca3f6161ec66574eea117b6c1da4db95d15214
Signed-off-by: Bradley Gorman <bgorman@au1.ibm.com>

Revert commit 84d1234e

 which was
inadvertently merged despite there being outstanding concerns.

Change-Id: Idbe47347e1008da28cd7730947c7225e74a12c5b
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

The secs parameter is of type number.  It will accept
values that seem invalid but Node.js actually enforces
a minimum and maximum value in setTimeout, so any value
will work.  Need to make this clear in the documentation.
https://jira.hyperledger.org/browse/FAB-126



Change-Id: Ia3e99037df45476492f3792ed23ca154fed95903
Signed-off-by: Caroline Daughtrey <cdaughtr@us.ibm.com>

Change-Id: Id812afcac32d08cff4403e52445469dbf2b91428
Signed-off-by: Gregory Haskins <gregory.haskins@gmail.com>

As currently (for backward compatibility) the 0th
element of args is passed as a function, Noop
chaincode needs to threat this is its only argument.

Change-Id: I5049db0210502355a3f11154e4bfaf04f9b2b17b
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Change-Id: Ic9ec62f4f009b34ad316ea753c46d365371ec401
Signed-off-by: jiangyaoguo <jiangyaoguo@gmail.com>