-
Notifications
You must be signed in to change notification settings - Fork 98
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Version 2.20.0-RC-v2-21.1.01 release (#186)
Co-authored-by: DevCenter-DocuSign <[email protected]>
- Loading branch information
1 parent
d2049d4
commit 1a50074
Showing
10 changed files
with
151 additions
and
125 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,94 +1,76 @@ | ||
# The Official DocuSign Java Client | ||
# The Official DocuSign eSignature Java Client SDK | ||
|
||
[![Build status][travis-image]][travis-url] | ||
[![Maven Central status][maven-image]][maven-url] | ||
|
||
## Requirements | ||
|
||
- Java 1.9+ | ||
- Free [Developer Sandbox](https://go.docusign.com/sandbox/productshot/?elqCampaignId=16531) | ||
* Java 1.9+ | ||
* Free [Developer Sandbox](https://go.docusign.com/sandbox/productshot/?elqCampaignId=16531) | ||
|
||
## Compatibility | ||
|
||
- Java 1.9+ | ||
|
||
## Note | ||
|
||
This open-source SDK is provided for cases where you would like to make additional changes that the SDK does not provide out-of-the-box. If you simply want to use the SDK with any of the examples shown in the [Developer Center](https://developers.docusign.com/esign-rest-api/code-examples), follow the installation instructions below. | ||
* Java 1.9+ | ||
|
||
## Installation | ||
This SDK is provided as open source, which enables you to customize its functionality to suit your particular use case. To do so, download or clone the repository. If the SDK’s given functionality meets your integration needs, or if you’re working through our [code examples](https://developers.docusign.com/docs/esign-rest-api/how-to/) from the [DocuSign Developer Center](https://developers.docusign.com/), you merely need to install it by following the instructions below. | ||
|
||
Note: DocuSign uses **Eclipse** with **Maven** for testing purposes. | ||
**Note:** DocuSign uses Eclipse with Maven for testing purposes. | ||
|
||
### Maven: | ||
|
||
1. In Eclipse, create a new project by selecting **File** -> **New** -> **Project**. | ||
2. In the **New Project Wizard** , expand **Maven** , then select **Maven Project.** | ||
1. In Eclipse, create a new project by selecting **File > New > Project**. | ||
2. In the New Project Wizard, expand **Maven,** then select **Maven Project.** | ||
3. Leave **Create a simple project** unchecked. | ||
4. Select **Next** , then provide a unique **Group** and **Artifact Id**. | ||
5. In the directory where you've saved your project, open the _pom.xml_ file. | ||
6. In the _pom.xml_ file, locate the **dependencies** node. | ||
7. Add: | ||
|
||
``` | ||
<dependency> | ||
<groupId>com.docusign</groupId> | ||
<artifactId>docusign-esign-java</artifactId> | ||
<version>2.19.0-RC2</version> | ||
</dependency> | ||
``` | ||
|
||
8. If your project is still open, restart **Eclipse**. | ||
4. Select **Next,** then provide a unique **groupId** and **artifactId.** | ||
5. In the directory where you've saved your project, open the pom.xml file. | ||
6. In the pom.xml file, locate the `dependencies` node. | ||
7. Add: | ||
``` | ||
<dependency> | ||
<groupId>com.docusign</groupId> | ||
<artifactId>docusign-esign-java</artifactId> | ||
<version>2.20.0-RC1</version> | ||
</dependency> | ||
``` | ||
8. If your project is still open, restart Eclipse. | ||
## Dependencies | ||
|
||
This client has the following external dependencies: | ||
- swagger:swagger-annotations:jar:1.5.8 | ||
- sun.jersey:jersey-client:jar:1.19.1 | ||
- sun.jersey.contribs:jersey-multipart:jar:1.19.1 | ||
- fasterxml.jackson.core:jackson-core:jar:2.9.9 | ||
- fasterxml.jackson.core:jackson-annotations:jar:2.9.9 | ||
- fasterxml.jackson.core:jackson-databind:jar:2.9.9 | ||
- fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.9.9 | ||
- fasterxml.jackson.datatype:jackson-datatype-joda:jar:2.1.5 | ||
- joda-time:joda-time:jar:2.9.3 | ||
- brsanthu:migbase64:jar:2.2 | ||
- apache.oltu.oauth2:org.apache.oltu.oauth2.client:1.0.2 | ||
- junit:junit:jar:4.12 | ||
|
||
## Code Examples | ||
|
||
### Launchers | ||
* swagger:swagger-annotations:jar:1.5.8 | ||
* sun.jersey:jersey-client:jar:1.19.1 | ||
* sun.jersey.contribs:jersey-multipart:jar:1.19.1 | ||
* fasterxml.jackson.core:jackson-core:jar:2.9.9 | ||
* fasterxml.jackson.core:jackson-annotations:jar:2.9.9 | ||
* fasterxml.jackson.core:jackson-databind:jar:2.9.9 | ||
* fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.9.9 | ||
* fasterxml.jackson.datatype:jackson-datatype-joda:jar:2.1.5 | ||
* joda-time:joda-time:jar:2.9.3 | ||
* brsanthu:migbase64:jar:2.2 | ||
* apache.oltu.oauth2:org.apache.oltu.oauth2.client:1.0.2 | ||
* junit:junit:jar:4.12 | ||
DocuSign provides a sample application referred to as a [Launcher](https://github.com/docusign/eg-03-java-auth-code-grant). The Launcher contains a set of 14 common use cases and associated source files. These examples use DocuSign's [Authorization Code Grant](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-code-grant) flow. | ||
## Code examples | ||
You can find on our GitHub a self-executing package of code examples for the eSignature C# SDK, called a [Launcher](https://github.com/docusign/code-examples-java/blob/master/README.md), that demonstrates common use cases. You can also download a version preconfigured for your DocuSign developer account from [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/). These examples can use either the [Authorization Code Grant](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-code-grant) or [JSON Web Token (JWT)](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-jsonwebtoken) authentication workflows. | ||
### Proof-of-concept applications | ||
## OAuth implementations | ||
For details regarding which type of OAuth grant will work best for your DocuSign integration, see [Choose OAuth Type](https://developers.docusign.com/platform/auth/choose/) in the [DocuSign Developer Center](https://developers.docusign.com/). | ||
If your goal is to create a proof-of-concept application, DocuSign provides a set of [Quick Start](https://github.com/docusign/qs-java) examples. The Quick Start examples are meant to be used with DocuSign's [OAuth Token Generator](https://developers.docusign.com/oauth-token-generator), which will allow you to generate tokens for the Demo/Sandbox environment only. These tokens last for eight hours and will enable you to build your proof-of-concept application without the need to fully implement an OAuth solution. | ||
|
||
## OAuth Implementations | ||
|
||
For details regarding which type of OAuth grant will work best for your DocuSign integration, see the [REST API Authentication Overview](https://developers.docusign.com/esign-rest-api/guides/authentication) guide located on the [DocuSign Developer Center](https://developers.docusign.com/esign-rest-api/guides/authentication). | ||
|
||
For security purposes, DocuSign recommends using the Authorization Code Grant flow. | ||
|
||
There are other use-case scenarios, such as **single page applications** (SPA) that use **Cross-Origin Resource Sharing** (CORS), or where there may not be a user to interact with your Service Account. For these use cases, DocuSign also supports [JWT](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-jsonwebtoken) and [Implicit](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-implicit) grants. For code examples, see the links below: | ||
|
||
- [JWT (JSON Web Token)](https://github.com/docusign/eg-01-java-jwt) | ||
- Implicit Grant (coming soon) | ||
For security purposes, DocuSign recommends using the [Authorization Code Grant](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-code-grant) flow. | ||
## Support | ||
|
||
Log issues against this client through GitHub. We also have an [active developer community on Stack Overflow](https://stackoverflow.com/questions/tagged/docusignapi). | ||
## License | ||
The DocuSign eSignature Java Client SDK is licensed under the [MIT License](https://github.com/docusign/docusign-java-client/blob/master/LICENSE). | ||
The DocuSign Java Client is licensed under the [MIT License](https://github.com/docusign/docusign-java-client/blob/master/LICENSE). | ||
|
||
### Additional resources | ||
* [DocuSign Developer Center](https://developers.docusign.com/) | ||
* [DocuSign API on Twitter](https://twitter.com/docusignapi) | ||
* [DocuSign For Developers on LinkedIn](https://www.linkedin.com/showcase/docusign-for-developers/) | ||
* [DocuSign For Developers on YouTube](https://www.youtube.com/channel/UCJSJ2kMs_qeQotmw4-lX2NQ) | ||
[travis-image]: https://img.shields.io/travis/docusign/docusign-java-client.svg?style=flat | ||
[travis-url]: https://travis-ci.org/docusign/docusign-java-client | ||
[maven-image]: https://img.shields.io/maven-central/v/com.docusign/docusign-esign-java.svg?style=flat | ||
[maven-url]: https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.docusign%22 | ||
|
||
[maven-url]: https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.docusign%22 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.