I meant that they were originally planned to be done for Java EE 8, via the JCP. So there was nothing to transition ;)
It's a past statement. I don't think there is much value to discuss what might have been included in Java EE 8.
Yes, and no. Yes, of course it's a past statement, but it does show that if these specs were planned to be in Java EE 8, they are a natural fit for Jakarta. It's not some wish that came around later.
Config, Health, Metrics, Fault Tolerance and JWT among others were all planned for Jakarta EE.
The first 4 were not done since at the time the issues at Oracle started, and essentially MicroProfile was created as an alternative. JWT was not included since I simply ran out of time for Security 1.0 (both OAuth and JWT were planned for 1.0). Then the entire transition to Eclipse happened, and in the meanwhile MP "hijacked" JWT (hijacked with a big ;)).
So it's no use to cry about spilled milk; what's done is done, but to reiterate, it's an explanation why Jakarta EE has a need/desire for those things.
I think moving MP Config to Jakarta while retaining the same namespace is a better option.
That would be my second choice, not so pretty, but I could live with it.
Kind regards,
Arjan
Hi
Yes, many and APIs were not intended to ever transition to the JCP.
I meant that they were originally planned to be done for Java EE 8, via the JCP. So there was nothing to transition ;)
Kind regards,
Arjan Tijms
cn4j-alliance mailing list
cn4j-alliance@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cn4j-alliance
--
_______________________________________________
cn4j-alliance mailing list
cn4j-alliance@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cn4j-alliance
