Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [config-dev] Config for Jakarta EE 12 and MP.next
Hi,

A few comments inline. Thank you!

Cheers,
Roberto

On 4 Feb 2025, at 18:18, Jared Anderson via config-dev <config-dev@xxxxxxxxxxx> wrote:

This email is a follow up to the discussion at the 2025-02-04 Jakarta EE platform call.
In that call, we discussed an approach where Jakarta EE 12 could effectively use MicroProfile Config "as is" with some important non-technical accommodations.
  1. The APIs for Jakarta Config would be the MicroProfile Config APIs, but with jakarta namespace. Yes, a copy/paste.

After the initial copy/paste, how would things evolve? Would Jakarta keep the APIs in-sync? What restricts Jakarta from using the API as-is? 

  1. The implementation may delegate to the MicroProfile Config implementation.
  2. 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.
  3. The TCK would be a copy/paste of the MicroProfile Config TCK and updating the name space and adding jakarta-config.properties testing
  4. 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

How about dropping microprofile-config.properties (keep it for compatibility) and jakarta-config.properties, and use application.properties? This one is already used by many popular runtimes like Spring, Quarkus, and Micronaut, to name a few. 

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
_______________________________________________
config-dev mailing list
config-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top