back to all blogsSee all blog posts

API and SPI Javadoc in Open Liberty

image of author
Michal Broz on Jul 25, 2023
Post available in languages: 日本語 ,

Concurrent with the Open Liberty release, the Javadocs in the Open Liberty docs are expanded to include the Liberty-specific APIs and SPIs. This update simplifies developing applications and custom features that use various Liberty capabilities, like OpenID Connect and OAuth. Also, various bugs were fixed as part of this release.

In Open Liberty

Run your apps using

If you’re using Maven, here are the coordinates:


Or for Gradle:

dependencies {
    libertyRuntime group: 'io.openliberty', name: 'openliberty-runtime', version: '[,)'

Or if you’re using container images:


Or take a look at our Downloads page.

Ask a question on Stack Overflow

Liberty API and SPI Javadoc

Before the Open Liberty release, developers who were working with Liberty APIs and SPIs had to use the embedded Javadoc that comes packaged with the runtime or build their own Javadocs from source. Starting with, we’ve added the API and SPI Javadoc to the Open Liberty Docs, alongside the Javadoc for MicroProfile, Jakarta EE, and Java EE. We’ve also retroactively added the Javadoc for

To start using the hosted Javadoc, navigate to the REFERENCE section of the Open Liberty Docs.

Notable bugs fixed in this release

We’ve spent some time fixing bugs. The following sections describe just some of the issues resolved in this release. If you’re interested, here’s the full list of bugs fixed in

  • GlobalOpenTelemetry is missing public methods

    Liberty overrides the GlobalOpenTelemetry class to return a no-op. Liberty does not allow users to set the class and, instead, CDI injection should be used to acquire an OpenTelemetry object.

    However the override is missing public methods, which causes an error to occur if called. For example:

    Caused by: java.lang.NoSuchMethodError: io/opentelemetry/api/GlobalOpenTelemetry.getPropagators()Lio/opentelemetry/context/propagation/ContextPropagators; (loaded from file:/home/gb110303/workspaces/open-liberty/dev/build.image/wlp/lib/ by org.eclipse.osgi.internal.loader.EquinoxClassLoader@7be84dfc[]) called from class io.opentelemetry.opentracingshim.OpenTracingPropagatorsBuilder (loaded from file:/home/gb110303/workspaces/open-liberty/dev/build.image/wlp/usr/servers/Telemetry10Shim/workarea/org.eclipse.osgi/52/data/cache/ by
    at OpenTracingPropagatorsBuilder.<init>(
            at OpenTracingPropagators.builder(
            at OpenTracingShim.createTracerShim(
            at OpenTracingShimServlet.createShim(
            at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(
            at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(

    This issue now resolved and calling a method on GlobalOpenTelemetry delegates to the no-op OpenTelemetry class.

  • Concurrency errors when using same JWT access token for inbound propagation

    For a Liberty server configured with the`openidConnectClient-1.0` feature and using the same JWT access token for inbound propagation for multiple requests, a concurrency error occurs that causes the requests to fail. This error results in a ConcurrentModificationException:

    Stack Dump = java.util.ConcurrentModificationException
            at java.util.LinkedList$ListItr.checkForComodification(
            at java.util.LinkedList$

    This issue has been resolved. The ConcurrentModificationException is not longer thrown and the requests succeed.

  • Update faces-4.0 to MyFaces 4.0.1

    The following issues are fixed in the 4.0.1 update:

    Note that some issues have already been addressed in earlier versions of Liberty, such as MYFACES-4594.

Get Open Liberty now