Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Java EE Guardians Statement on Oracle/Eclipse Agreement
As part of the Java EE Guardians, I agree with the statement sent out.  I would like to see a big-bang change for the new naming convention to avoid confusion and make releases faster.  I think any decision made to speed up the development process benefits everyone in the long run.

Regards,
Wesley

On Wed, Jun 5, 2019 at 9:48 AM Ralph Soika <ralph.soika@xxxxxxxxx> wrote:
Hi Ryan,

here is my opinion concerning the Java EE transition to Jakarta EE:

  • javax* should be replaced by jakarta* at a one-time, immediate transition!
    Get rid of old things and show the community that a new platform is rising (I know that technical this is not so easy as it sounds)
  • Jakarta EE 9 should contain the core components (EJB, JSF, Servlet, Jax-Rs, CDI) and made it available sooner
    We do not need to support backward compatibility in this situation. Everyone who need to ran a legacy application can use one of the available Java EE Application servers.
  • Jakarta EE should include the Eclipse Microprofile APIs : Config, Metrics, Health and fault-tolerance in its core.
    In long-term Microprofile should become part of Jakarta EE.
    For now most Open Application Servers (OpenLiberty, Payara, Wildfly) already support Microprofile and so if Jkarata EE 9 does not include Microprofile in its core spec, this is not the biggest problem



===
Ralph
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top