September 18 All code required for GF build contributed.
September 23 Eclipse GlassFish builds.
October 1 Java EE 8 CTS testing. We are able to run CTS tests on Eclipse GlassFish.
October 22 ⚡
CI/CD release pipelines completed.
October 22 Eclipse GlassFish 5.1-RC1 milestone release.
November 5 ⚡ Dependencies updated. All projects are released to OSSRH and have dependencies to Eclipse version of other components.
November 30 ⚡ Release Review completed.
December 14 ⚡ Eclipse GlassFish 5.1 release. All CTS tests are passed.
There is a lot of work to do, so every contribution is appreciated, especially regarding setting up the CI/CD pipelines for all the EE4J projects. Take a look at our status sheet and sign up where you think you can contribute.
SnoopEE [ˈsnuːpı] –The lean and simple discovery mechanism for Java EE based microservices.
What’s in a name, really?
Naming is hard! When I came up with the name Snoop for my discovery mechanism for microservices based on Java EE, my though was to associate the name with “snooping around for services to discover”. It seems, however, that most people’s thought goes to Snoop Dogg when hearing the name and that was never my intention.
That is one of the reasons for the renaming. Another consideration is that I want to point out that the best fit for SnoopEE is for Java EE!
At the same time I don’t want to signal that it is only for Java EE. I want it to be just as lean and simple no matter what technology used to implement the services. That is the only reason why I have been a little reluctant to the renaming.
SnoopEE has a nicer feel and as the twitter poll indicates, I am not alone thinking this.
For the record, I have nothing at all against Snoop Dogg! I just feel that Snoopy the dog is a little bit cuter…
I have crated a new page for SnoopEE, but as for everyhing else, such as GitHub repo, maven coordinates and naming, it all stays as it is until properly announced otherwise.
The work in the Expert Group for JSR 371 progresses and here is a small update. A couple of decisions have been made and the most important one is that the JSR will be layered on top of JAX-RS. The decision was made by voting between this and the alternative of layering it on top of the Servlet API.
What this means for you as a developer is that the stuff you are familiar with from JAX-RS is directly transferable to MVC. As you can see in the simple example below, the only thing that differs from JAX-RS is the @Controller and @View annotations.
Note that this code is highly experimental and will most likely change as the work with the specification continues.
Earlier this week, my talk on Spring 4, Java EE 7 or Both was accepted and added to the program for JEEConf. Even with the current situation in Ukraine, I am looking very much forward to going there. We should never let politics interfere with our knowledge sharing and community activities. See you there!