| Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76 |
This isn't very accurate. Payara (Server and Micro) are targeting the next release for MP 1.2 support, as we've announced previously and we are currently working on 1.3 specs.
MicroProfile is a very fast moving specification and it's natural for there to be some lead time in implementing some specifications. MP 1.3 has only been released for less than a month, so to use that as evidence that specs are not "likely to see broader vendor support" is misleading.
Mike Croft Java Middleware Consultant Payara Services Limited
Payara Server: Derived from GlassFish with 24/7 Production Support
---------------------------------------------------------------------------------------------------------------------------- Payara Services Limited, Unit 11, Malvern Hills Science Park, Geraldine Road, Malvern, Worcestershire, WR14 3SZ
From: ee4j-community-bounces@xxxxxxxxxxx <ee4j-community-bounces@xxxxxxxxxxx> on behalf of Werner Keil <werner.keil@xxxxxxxxx>
Sent: 21 January 2018 15:44:50 To: EE4J community discussions Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76 CDI itself, Bean Validation or Ozark have also been Apache only and at least Ozark/MVC did, too.
Whatever the PMC decided when incorporating all that, it should be possible to integrate field studies at MicroProfile into EE4J for wider adoption.
Nobody really implements most of the new MP features, except a single vendor maybe, sometimes specs or APIs don't have any implementation.
Payara Micro has not gone beyond MP 1.1 and https://www.payara.fish/payara_micro shows only a few others are supported. Rest Client isn't, It is likely to see a broader vendor support in EE4J / a future
JAX-RS spec for sure.
Werner
On Sat, Jan 20, 2018 at 7:44 PM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to |