The next version of the Microsoft Graph Java\/Android SDK is now available for preview! Leverage new modern development features when integrating your application with Microsoft Graph.<\/p>\n
This new version of the SDK includes the following improvements:<\/p>\n
Try out this new preview version today and let us know what you think<\/a>! See the following instructions to add the new SDK to your project.<\/p>\n Edit the \u201cbuild.gradle\u201d file of your project to contain the following entries<\/p>\n In the “repositories” section:<\/p>\n In the “dependencies” section<\/p>\n In the \u201cpom.xml\u201d file under the project node:<\/p>\n In the \u201cpom.xml\u201d file under the dependencies node:<\/p>\n This section includes examples of some of the improvements in this new version.<\/p>\n Thanks to Azure Identity, the Microsoft Graph Java SDK now supports device code flow. This flow is ideal for devices that have limited input capabilities like IoT devices, TVs, wearables, and more.<\/p>\n To use this new authentication flow and query Microsoft Graph with the Java SDK, simply add the following lines to your application.<\/p>\n CompletableFuture<\/strong> are a standard and simple way of deferring asynchronous code to another thread. By doing so, you avoid blocking the main thread to wait on some network, IO or CPU intensive operation. This is especially important when building applications with a Graphical User Interface (GUI) to avoid having the interface freeze on each call allowing you to deliver a better user experience. This is also important for backend server applications to allow the main thread to continue working and support more incoming customers requests instead on waiting for completion, allowing for more throughput.<\/p>\n The new asynchronous API surface in the SDK is denoted with an \u201cAsync\u201d suffix and it automatically runs the code in a background thread pool for you.<\/p>\n The new SDK now provides a ParameterSet<\/strong> class for each method allowing developers to fine-tune the parameters to provide the OData method (actions & functions). This new ParameterSet<\/strong> object also allows developers to use OData methods overloads.<\/p>\n For example:<\/p>\n This approach allows developers to specific any parameter by using the \u201cwithParameterName\u201d methods on the ParameterSet <\/strong>builder.<\/p>\nGradle<\/h4>\n
maven { url 'https:\/\/oss.sonatype.org\/content\/repositories\/snapshots' }<\/pre>\nimplementation 'com.microsoft.graph:microsoft-graph-core:2.0.0-SNAPSHOT'\nimplementation 'com.microsoft.graph:microsoft-graph:3.0.0-SNAPSHOT'<\/pre>\n
Maven<\/h4>\n
<profiles>\n \u00a0<profile>\n \u00a0\u00a0\u00a0 <id>allow-snapshots<\/id>\n \u00a0\u00a0\u00a0 <activation><activeByDefault>true<\/activeByDefault><\/activation>\n \u00a0\u00a0\u00a0 <repositories>\n \u00a0\u00a0\u00a0\u00a0\u00a0 <repository>\n \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0<id>snapshots-repo<\/id>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <url>https:\/\/oss.sonatype.org\/content\/repositories\/snapshots<\/url>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <releases><enabled>false<\/enabled><\/releases>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <snapshots><enabled>true<\/enabled><\/snapshots>\n \u00a0\u00a0\u00a0\u00a0\u00a0 <\/repository>\n \u00a0\u00a0\u00a0 <\/repositories>\n <\/profile>\n<\/profiles><\/pre>\n
<dependency>\n <groupId>com.microsoft.graph<\/groupId>\n <artifactId>microsoft-graph<\/artifactId>\n <version>3.0.0-SNAPSHOT<\/version>\n<\/dependency><\/pre>\n
Major improvements showcase<\/h3>\n
Device code flow support<\/h4>\n
final DeviceCodeCredential deviceCodeCredential = new DeviceCodeCredentialBuilder()\n \u00a0\u00a0 .clientId(CLIENT_ID) \/\/ the client id of your application registration\n \u00a0\u00a0 .challengeConsumer(challenge -> {\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ lets user know of the challenge\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 System.out.println(challenge.getMessage());\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 })\n \u00a0\u00a0 .build();\n\nfinal TokenCredentialAuthProvider authProvider = new TokenCredentialAuthProvider(SCOPES, deviceCodeCredential);\nfinal GraphServiceClient graphClient = GraphServiceClient.builder().authenticationProvider(authProvider).buildClient();<\/pre>\nCompletableFuture API surface<\/h4>\n
graphClient.me().drive().buildRequest().getAsync().thenApply(result -> {\n \u00a0 System.out.println(\"Found Drive \" + result.id); \/\/ this method will be called once the request is completed\n}); \/\/ the main thread continues execution after starting the request<\/pre>\nFluent API for methods parameters & optional parameters support<\/h4>\n
graphClient.me().drive().items(\"{id}\").workbook().worksheets(\"{id|name}\")\n.range(WorkbookWorksheetRangeParameterSet.newBuilder().withAddress(\"A1:B2\").build());<\/pre>\nNext steps<\/h3>\n