JAX-RS Build Pipeline Webcast

This week I explained the JAX-RS Build Pipeline in a Web Cast hosted by Ed and Dmitry. If you missed it, you can watch the recording on YouTube: https://www.youtube.com/watch?v=J5qLpTcRgH0.

Advertisements

JAX-RS 2.1.1 Available on Maven Central

I am very proud to announce that I just pressed the button: JAX-RS 2.1.1 was released by the committers of the Eclipse Project for JAX-RS and now is available on Maven Central. While this is just a collection of small bug fixes, it is a huge step for the community, as this is the first release of Java’s REST API under the auspices of the Eclipse Foundation, and the very first JAX-RS release technically performed by a non-Oracle committer. This proofs community is in control and able to deliver! Can’t wait to see which other EE4J subproject is next!

If you are interested in our next steps, follow my blog. BTW, if you have questions on JAX-RS 2.1.1 or the future, just use the comments function to ask!

EclipseCon Europe 2018: I’m Speaking!

Come to Ludwigsburg / Germany if you are interesting in my co-talk with Kevin Sutter (IBM) about JAX-RS and Jakarta EE under the auspieces of the Eclipse Foundation.

JAX-RS 2.2-SNAPSHOT @ JFS 2018

Just back from Java Forum Stuttgart 2018, I want to share the great feedback you all gave me while and after my (and Heiko’s) presentations on JAX-RS (and MicroProfile).

In my talk, I (for JAX-RS project, and and my co-host Jake, an inofficial mascot of Jakarta EE) reported about the last six months of JAX-RS being under EF control, how the migration worked out, how we work together, our current status and future targets. Heiko Rupp (for Red Had / Microprofile WG) gave a great live coding introduction into Microprofile APIs.

The audience (approx. 200 in the overcrowded room, out of approx. 2000 attendees of the conference) was following my report somewhat “devoutly”, and the questions were really precise. I had the impression that the audience is really interested in what we do, how we do it, and our roadmap. I demonstrated the one-second boot time using the new Java SE Bootstrap (ontop of Jersey 2.28-SNAPSHOT) which they really seem to like. In particular, I had the impression that it was impressive to see the boot time difference to the “usual” micro server approach Heiko Rupp demonstrated in his talk about current status of Microprofile set of APIs using Thorntail aka Wildfly Swarm (more than ten seconds boot time). Also the audience seems to like our proposed schedule, in particular getting 2.2 rather soon and then having CDI in 3.0.

Later on I had the chance to give more live presentations at the booth of iJUG (Association of German-speaking JUGs) and the guests really liked the simplicity of tha Java SE approach. In particular, the combination of one second boot time and debugging their application in-process in Eclipse IDE (in comparison to ten seconds boot time and remote debugging using a full-monty server).

What people really miss is binaries to try it out. They like to get binary access to the bootstrap API and implementation of that. Hence, I have to speed up my work on the nightly builds and Jersey PoC. Also I feel it is expected by the majority of users that some or all Microprofile APIs should get moved under the auspieces of the Jakarta EE WG so they do not stand “aside” of the “official” enterprise standard-to-come. This would allow to directly integrate e. g. JAX-RS’s Java SE Bootstrap API (i. e. a soon-to-come official Jakarta EE Standard) with Microprofile’s Config, Health and Metrics APIs (i. e. non-Jakarta EE standards). At the moment this is not feasible, as Microprofile APIs’s relationship to Jakarta EE is nother better- or worse-related compared to e. g. commonly used Apache libaries unfortunately. That is a point the PMCs clearly need to focus on in 2019.

To sum up, this was the litmus test of our project and we succeeded. Next we need are nightly builds, which is on the way (I’m preparing this currently, PR will follow soon), and then JAX-RS’s initial EE4J_8 release to make the track free for JAX-RS 2.2.

Hi, I’m Jake!

Hello everybody, my name is Jake, I drink Java, and I am a professional mascot!

I was born in a German Cinema 4D Studio, and I am fully flexible: You can bend and shake and twist me. I have a realistic fur imitation and I’m completely rigged. My authors even gave me an experimental CMotion walking cycle, so I can jump around. I’m really great. I am cute and photogenic and I’m used to get professionally lighted. I look good on shirts and in the web, and I am open source: My home is GitHub. I am neither trademarked nor otherwise limited and I’m licenced under EPL 2.0.

At the moment I am unemployed. I just do temp jobs on my artist’s blog to get along, but this really isn’t fulfilling. I want a real job. And I want to go to Jakarta. I hope really badly that soon there will be some casting for a Jakarta EE mascot. This would be my dream! Even without, I can work for you. Trust me, I’m the right one to pimp your next slide deck, conference trailer, or project stickers!

So, to sum up: Pick me! I’m cute!

jax-rs@Eclipse @ Java Forum Stuttgart 2018

As part of the first batch, Oracle provided JAX-RS to the Eclipse Foundation. And now? What  happened since then? What will come in future? Is Oracle bailing out? Who chimed in? And when will there be JAX-RS 2.2 or 3.0?

As a JAX-RS Committer member, I will answer lots of these questions in my talk at Java Forum Stuttgart July 4th 2018.

Microsoft joins Jakarta EE working group

Today Bruno Borges, Principal Developer Advocate for Java at Microsoft, announced that his company likes to join the Jakarta EE working group. Why this is worth a note? Because Jakarta EE is the new trade name of the industrial standard formerly known as Java EE (Java Enterprise Edition) and Microsoft -at least so far- did not have a product implementing this complete umbrella standard (it did support only few bricks).

I once said that Microsoft will get rid of Windows in favor of Linux, and this is happening right now. I also once said that Microsoft will drop C# and Dotnet in favor of Java and Java EE. So maybe you understand now, why I think this is exciting news!