One goal of MDAccess for OSLC 3.0 was to upgrade its third-party libraries, to avoid using a library version having known vulnerabilities, and to no longer require libraries that are obsolete.
While every effort was made to avoid breakage, there are a few areas of incompatibility or new APIs that should be adopted by clients. This document describes those areas and provides instructions for migrating plug-ins to 3.0.
Refer to the Third-Party Libraries page for details on the new set of required libraries.
MDAccess for OSLC uses SLF4J for logging messages. In previous version, MDAccess for OSLC also had a dependency on Apache Log4j and tried to initialize the Log4j configuration on its own. This is no longer the case, clients may use any SLF4J compliant logging implementation of their choice.
log4j.configurationsystem property for Log4j, or a
logback.configurationFilesystem property for Logback.
In previous version, MDAccess for OSLC was using Apache Wink Client to act as a client for requesting OSLC resources. This library is now retired and MDAccess for OSLC no longer depends on it.
com.sodius.oslc.client.requests.GetResourcesto set as third parameter the type of resource to obtain, e.g.
Collection<Configuration> resources = new GetResources(client, uri, Configuration.class).get();
com.sodius.oslc.client.ClientResponsewhen a collection of resources is desired, e.g.
Collection<Configuration> resources = clientResponse.getEntities(Configuration.class);
In previous version, MDAccess for OSLC was using Apache Wink JSON4J for processing JSON content. This library is now retired and MDAccess for OSLC no longer depends on it. MDAccess for OSLC now uses Jakarta JSON as a replacement.