In that call, we discussed an approach where Jakarta EE 12 could effectively use MicroProfile Config "as is" with some important non-technical accommodations.
-
The APIs for Jakarta Config would be the MicroProfile Config APIs, but with jakarta namespace. Yes, a copy/paste.
-
The implementation may delegate to the MicroProfile Config implementation.
-
The Spec document would be one-line: see the corresponding MicroProfile config spec document. May need additional text to talk about the difference in namespace and adding in jakarta-config.properties until a new MP Config version added that to its specification.
See #5 below.
-
The TCK would be a copy/paste of the MicroProfile Config TCK and updating the name space and adding jakarta-config.properties testing
-
Need to introduce a new line in the
ConfigSource
(MicroProfile Config API)
-
“Some configuration sources are known as default configuration sources. These configuration sources are normally available in all automatically-created configurations, and can be manually added to manually-created configurations as well. The default configuration
sources are:
-
1. System properties, with an ordinal value of 400
-
2. Environment properties, with an ordinal value of 300
-
3. The /META-INF/jakarta-config.properties resource, with an ordinal value of 200
-
4. The /META-INF/microprofile-config.properties resource, with an ordinal value of 100
Let's continue discussion using this "both lists on the To: line" approach rather than introduce another venue, such as the cn4j
mailing
list (
eclipse
archive).
Sincerely,
Ed Burns and Jared Anderson
Jakarta EE 12 release co-coordinators
