Releases: inrupt/solid-client-java
1.0.0.Beta2
This is the second beta release of the Inrupt Client Libraries for Java.
The Inrupt Client Libraries are designed to make it easier for developers to interact with Solid Resources. The libraries provide a session management abstraction that supports OpenID Connect tokens as well as Access Grants. In addition, there are mechanisms for mapping RDF-based resources into domain-specific Java objects.
Features
Below is a summary of the new features included in this release:
- The
SolidContainerclass has a new method:getResources(), which returns aSet<SolidResource>. - The SpringBoot example application now supports OpenID Connect authentication using a Solid WebID.
Full Changelog: v1.0.0.Beta1...v1.0.0.Beta2
Upgrade notes
- As part of #400, the
SolidContainer::getContainedResourcesis now deprecated. Users should now useSolidContainer::getResources, which returns aSet<SolidResource>rather than aStream<SolidResource>. - As part of #401, the Maven
groupIdhas changed tocom.inrupt.client. All users of the Java Client Libraries should now use Maven coordinates such as:
<dependency>
<groupId>com.inrupt.client</groupId>
<artifactId>inrupt-client-api</artifactId>
<version>1.0.0.Beta2</version>
</dependency>
1.0.0.Beta1
This is the first beta release of the Inrupt Client Libraries for Java.
The Inrupt Client Libraries are designed to make it easier for developers to interact with Solid Resources. The libraries provide a session management abstraction that supports OpenID Connect tokens as well as Access Grants. In addition, there are mechanisms for mapping RDF-based resources into domain-specific Java objects.
Features
Below is a summary of the new features included in this release:
- Support for non-RDF resources in the high-level client API #368
- This feature introduces the following new classes in the
inrupt-client-apipackage:RDFSource,NonRDFSource - And, in the
inrupt-client-solidpackage:SolidRDFSource,SolidNonRDFSource
- This feature introduces the following new classes in the
- Convenience methods for deleting resources using only a URI #376
- Improved flexibility of the
SolidContainerclass #373 - Return the modified object in the high-level client API for
createandupdate#377
Full Changelog: v1.0.0.Alpha7...v1.0.0.Beta1
Upgrade notes
- As part of #368, the class/interface structure has changed for the high-level client API.
com.inrupt.client.Resourceis now an interface, as iscom.inrupt.client.solid.SolidResource. Any code that previously used these classes should now usecom.inrupt.client.RDFSourceandcom.inrupt.client.solid.SolidRDFSource, respectively. - As part of #377, the high-level client API signature for
createandupdateno longer returns aCompletionStage<Response<Void>>. Now, these methods return the modified object:<T extends Resource> CompletionStage<T>.