Skip to main content

MicroProfile Config 3.1

MicroProfile Config provides a way to achieve this goal by aggregating configuration from many different ConfigSources and presents a single merged view to the user. This allows the application to bundle default configuration within the application. It also allows to override the defaults from outside or erase the property by simply specifying the property name without providing a value or an empty string as the value, e.g. via an environment variable a Java system property or via a container like Docker. MicroProfile Config also allows users to implement and register their own configuration sources in a portable way, e.g. for reading configuration values from a shared database in an application cluster.

Functional changes

A full list of changes delivered in the 3.1 release can be found at MicroProfile Config 3.1 Milestone.

Incompatible Changes

no

API/SPI Changes

no

Other Changes

  • TCK tests assume empty bean.XML is discovery mode ALL (765)
  • Make the TCK tests CDI 4 compatible (742)
  • TCK: MissingValueOnObserverMethodInjectionTest fails for a different reason (543)
  • Spec of precedence for sources when using profiles seems vague (781)

Maven coordinates

<dependency>

  <groupId>org.eclipse.microprofile.config</groupId>

  <artifactId>microprofile-config-api</artifactId>

  <version>3.1</version>

</dependency>

Scope

Released

Released

Details

TCK

Compatible Implementations

Open Liberty

Product
Java version
Open Liberty 23.0.0.10-beta
Java 11, Java 17
Open Liberty 23.0.0.12
Java 11, Java 17
Open Liberty - 24.0.0.9-beta-cl240920240801-0303
Java 11, 17 and 21

Helidon

Product
Java version
Helidon 4.1
Java 21 or higher

WebSphere

Product
Java version
IBM WebSphere Liberty 23.0.0.12
Java 11, Java 17

Payara Services Ltd

Product
Java version
Payara Server Enterprise 6.12.0
Java 11
Payara Server Community 6.2024.3
Java 11
Payara Server Community (Web Profile) 6.2024.3
Java 11
Payara Server Enterprise (Web Profile) 6.12.0
Java 11

Ballots

Plan Review

The Specification Committee Ballot concluded successfully on 2023-06-14 with the following results.

Representative Representative for: Vote
Summers Pittman, Vincent Mayers Atlanta JUG +1
Emily Jiang, Nathan Rauh IBM +1
Ed Bratt, Dmitry Kornilov Oracle +1
John Clingan, Roberto Cortez Red Hat +1
David Blevins, Jean-Louis Monteiro Tomitribe +1
Chandra Guntur, Michael Redlich Garden State Java User Group +1
Jan Westerkamp, Heiko W. Rupp iJUG -1
Kenji Kazumura, Takahiro Nagao Fujitsu +1
Alfonso Altamirano, Luís Neto Payara +1
Mingyue Huang Primeton +1
Reza Rahman, Edward Burns Microsoft +1
Total 10
Non-binding Vote Role Vote
Jean-Louis Monteiro +1
Total 1

Release Review

The Specification Committee Ballot concluded successfully on Mon, 9 Oct 2023 with the following results.

Representative Representative for: Vote
Vincent Mayers Atlanta JUG +1
Emily Jiang, Nathan Rauh IBM +1
John Clingan, Roberto Cortez Red Hat +1
David Blevins, Amelia Eiras Tomitribe +1
Chandra Guntur, Michael Redlich Garden State Java User Group +1
Ed Bratt, Dmitry Kornilov Oracle +1
Jan Westerkamp, Heiko Rupp iJUG -1
Kenji Kazumura, Takahiro Nagao Fujitsu +1
Reza Rahman, Ed Burns Microsoft +1
Mingyue Huang Primeton +1
Alfonso Altamirano, Luis Neto Payara +1
Feng Wang Asiainfo Anhui +1
Total 11
Non-binding Vote Role Vote
Emerson Castaneda Community +1
Total 1

Help optimize Enterprise Java for a microservices architecture.

Join the MicroProfile Google Group, peruse recent topics or create your own, and join in on the conversation. It's that easy!

JOIN THE DISCUSSION