Microprofile and Jakarta cooperation

[rixterd2]

Greetings,

Please direct me to a right place to ask questions if this is not the appropriate one.

Questions :

1. What is the current state of relationship between Jakarta and Microprofile ? Is it a cooperative or competetive environment ?
2. Are there any goals on adopting https://github.com/eclipse/microprofile-fault-tolerance or making new Jakarta specification ?

Regards,
Vladimir

[OndroMih]

Hi, @rixterd2,

Don't take my words as an official statement, I don't represent Jakarta EE or Microprofile, although I'm involved in them. I would say that it's rather cooperative relationship, although very loose. Normally, MicroProfile specifications stay in MicroProfile, unless there's an agreement to do something with them. For example, there's an ongoing effort on Jakarta Config specification, based on MP Config, which aims to bring Config into Jakarta EE and replace MP Config. There's MP JWT bridge specification, which doesn't bring anything to Jakarta EE, but allows products that support both MP and Jakarta EE to integrate them better in security area. The next obvious step is to move MP Rest Client to Jakarta EE, because it reuses a lot of Jakarta Rest APIs and nicely fits into Jakarta Rest. I'm not sure about Fault Tolerance, I don't think there's much support for moving it to Jakarta EE, it's one of the less popular MP specs, so I expect it will stay where it is.

This is, however, not the best place to discuss this. It's better to start a discussion on the Jakarta EE community mailing list or Slack, see: https://jakarta.ee/connect/

[anbusampath]

1. What is the current state of relationship between Jakarta and Microprofile ?

As per recent messages, MicroProfile specifications would be moved under Jakarta EE.

https://www.eclipse.org/lists/microprofile-wg/msg02797.html
https://www.eclipse.org/lists/microprofile-wg/msg02798.html

[rixterd2]

Thank you