I’m proud to be one of the first people ever speaking on the brand-new conference “Jakarta One” in 2019. The conference is a free livestream. Attend on September 10 when I’m talking about the Status Quo and Roadmap of JAX-RS!
If you are interested in writing lightweight RESTful Microservices implemented by just using JAX-RS (Jakarta RESTful Web Service) but no proprietary features or vendor-specific frameworks at all, then you definitively have to visit my seesion at EclipseCon Europ 2019!
Thank you to the great audience at Java Forum Stuttgart 2019! You asked me to upload my source code and slides. So here it is…:
Slides on Speakerdeck: https://speakerdeck.com/mkarg/jax-rs-3-dot-0-the-next-generation
Source Code on GitLab: https://gitlab.com/mkarg/jfs2019
If you have any questions just drop me a note: markus@headcrashing.eu. 🙂
I almost forgot to tell you: I have set up nightly buils of JAX-RS 2.2!
All you need to get in touch with the new binaries is to add the Eclipse Foundation’s SNAPSHOT repository to your Maven configuration, e. g.:
<project> <repositories> <repository> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> <id>repo.eclipse.org</id> <name>Eclipse Snapshots</name> <url>https://repo.eclipse.org/content/repositories/snapshots</url> </repository> </repositories> </project>
Beware of the fact that Oracle forced us to rename a lot of stuff, so you have to refer to the Maven GAV coordinates jakarta.ws.rs:jakarta.ws.rs-api:2.2-SNAPSHOT and all classes are in the jakarta.ws.rs package namespace now! Unfortunately Jersey, the former RI of JAX-RS, is still working on their 2.29 release which is JAX-RS 2.1 still, so you won’t be able to actually run anything using this new names. But I am confident that once 2.29 is out, they will eagerly pick up the changed names, so you can (again) try out all the great stuff we have in JAX-RS 2.2.
It is kind of a tradition meanwhile: To get the hottest news on JAX-RS 2.2 and 3.0 directly from one of the key committers, come again to Stuttgart on July 4 and visit my talk on “JAX-RS 3.0: The Next Generation”. This is not your dad’s JAX-RS anymore!
Thanks to all the nearly 100.000 readers of my last blog posting for the more than 111.000 views in one week! It seems I am not the only one caring about Java EE! This proofs that Java is everything but dead! 🙂
Today Eclipse Foundation’s president Mike Milinkovic blogged about the final result of the confidential trademark negotiations between Oracle and the Eclipse Foundation. As we remember, Oracle announced that Java EE will be open sourced to that organization and it would become true open source. After 18 months of intensive negotiations the effort has come to an end: It failed. There will be no trademark agreement.
The reason simply spoken is, according to the recent board meeting minutes, that Oracle wanted to have in turn a set of inacceptable demands. Some of them would put the existence of the Eclipse Foundation at severe risk. Oracle claimed that products distributed by the Eclipse Foundation (like the Eclipse IDE) must only be bundled with Java runtimes certified particularly by Oracle and its licencees — not any other vendor’s certification and not any uncertified runtime. Hence, the IDE and GlassFish wouldn’t be vendor-neutral products anymore. This restriction was not told at the start of the negotations, it was introduced much later, while the transfer was already in progress. One could assume that it was a reaction upon the donation of IBM’s OpenJ9 JVM, which is a clear threat to Oracle’s Java business. But once Eclipse products would be not vendor-neutral anymore, the EF’s tax exemption might become void, which would mean a financial fiasco, or possibly mean the end of the organization as a hole. Hence, it not only was inacceptable, but it was simply impossible to agree to Oracle’s requests, so the negotiations more or less completely failed.
What is left over is not more but also not less the end of Java EE. The Eclipse Foundation may use some rather outdated code, but must not modify it. If it gets modified, it must be renamed – both, the project name (like JAX-RS, which is not nice but acceptable) but also the package name (like javax.*), which means, existing applications will not run on the updated platform without recompilation of the application after intensive refactoring. Hence, it will become a completely new and incompatible platform, the worst case possible, as it not only voids the “WORA” (Write Once Run Anywhere) principle, it simply won’t happen in reality: After 18 months virtually no application vendor really wants to spend the time and money to update all customers with recompiled versions just for the sake of a renamed platform with a dubios future. The future is unclear because Oracle already started a blocking politics at the Eclipse Foundation’s board, where Oracle has a seat, and where unanimous decisions are needed. Oracle now has the power, and apparently will use that power, to block the foundation’s future. It demonstrated that power already in a board meeting, where they had the sole vote against an otherwise unaimous move.
The current reaction of the Eclipse Foundation is to demonstrate success to rescue at least some value of the intensively marketed Jakarta trademark. But at what price? For what keeping a trademark that became an empty hull now? It now is not the successor of Java EE as a global standard anymore, it is just some framework made by some foundation, and users eventually will learn and draw conclusions. Currently plans have intensivated to rename everything ASAP. But who will actually jump on that train, when it implies changing all existing applications? Eclipse’s Mike Milinkovic still sees the future bright. For me, the glass is not just half-empty anymore: Today it cracked into pieces. This is the day when Java EE was killed by Oracle.
