In case you missed it, Jakarta EE is officially out! Java EE was given a new home at the Eclipse Foundation and on February 26, 2018 Jakarta EE was chosen as the new name for Java EE. Join us at the next online DevNation Live Tech Talk on Thursday, May 3rd at 12pm EDT. The topic is “Jakarta EE: The Future of Java EE” presented by Dr. Mark Little, and hosted by Burr Sutter.
Java EE has been the dominant enterprise Java standard for well over a decade. With the release of Jakarta EE, we all have a chance to collaborate and build on the good things it inherits, while working to evolve those pieces that were perhaps never quite what was needed.
What does this mean for the future of enterprise Java and traditional Java application servers? Join us to gain an understanding of where Jakarta EE is heading and how you can help drive the future of enterprise Java.
Register now and join the live presentation at 12pm EDT, Thursday, May 3rd.
Continue reading “Next DevNation Live: Jakarta EE: The Future of Java EE, May 3rd, 12pm EDT”
Jakarta EE is officially out! OK, given the amount of publicity and evangelizing we and others have done around EE4J and Jakarta EE over the past few months you would be forgiven for thinking it was already the case but it wasn’t… until today!
I cannot stress enough how important this is to our industry. The number of Java developers globally is estimated at over 14 million. The Java EE market is estimated at a high multi-billion Dollar value to the industry. Yes there are other languages out there and other frameworks but none of them have yet made the impact Java and Java EE has over the years. Of course Java EE was not perfect for a variety of reasons, but if you consider how much of an impact it has had on the industry given known and debated limitations, just imagine how much it can bring in the years ahead if it were improved.
Continue reading “Jakarta EE is officially out”
The OpenShift Online Starter platform is available for free: visit https://manage.openshift.com/. It is based on Red Hat OpenShift Container Platform 3.7. This offering allows you to play with OpenShift Container Platform and deploy artifacts. The purpose of the article is to describe how to use Red Hat JBoss Developer Studio or JBoss Tools together with this online platform.
Continue reading “Develop and Deploy on OpenShift Online Starter using Red Hat JBoss Developer Studio”
JBoss Tools 4.5.1 and Red Hat JBoss Developer Studio 11.1 for Eclipse Oxygen.1A are here waiting for you. Check it out!
Continue reading “Announcing Red Hat Developer Studio 11.1.0.GA and JBoss Tools 4.5.1.Final for Eclipse Oxygen.1A”
JBoss Tools 4.5 and Red Hat JBoss Developer Studio 11.0 for Eclipse Oxygen are here waiting for you. Check it out!
Continue reading “Announcing Red Hat Developer Studio 11.0.0.GA and JBoss Tools 4.5.0.Final for Eclipse Oxygen”
In the previous part of this blog, I talked about the most important steps to get your project to compile with the latest Framework version.
The migration has been done through the first three steps mentioned here, and in this post, I will go over the least complicated steps of migration. Steps 4 and 5 cover the modernization of your project with the latest Framework 8 features. If you are in a hurry, you can do this later on as well, and use the new APIs only for new Vaadin code.
- Upgrade dependencies in the POM file
- Run Maven goal vaadin:upgrade8
- Upgrade Add-ons
- Upgrade non-data components
- Upgrade data components
- Back to the future
Continue reading “Upgrading to Vaadin Framework 8 (Part 2 of 2)”
In my previous post in the series, I discussed some fairly surface-level differences between C#/.NET and Java. These can be important for Java developers transitioning to .NET Core, to create code that looks and feels “native” to the new ecosystem. In this post, we dig beneath the surface, to understand .NET’s type system. It is my belief that, with Java in the rear view mirror, the .NET type system is more effective and enjoyable to write on. But you be the judge.
Continue reading “From Java to .NET Core, Part 2: Types”
JBoss Enterprise Application Server 7 has been out since June, and if you build and deliver using a Java EE environment and haven’t yet upgraded to EAP7, it’s time to make the jump.
Here’s a look at what’s new in JBoss EAP 7, what has changed since JBoss EAP 6, and how to get the most out of JBoss EAP 7 as your Java EE7 server.
JBoss EAP 7 is bassed on WildFly Application Server 10, which provides a complete implementation of the Java EE 7 Full and Web Profile standards. WildFly 10 does much to simplify modern application delivery based on containers and microservices.
JBoss EAP 7 features certified support for Java EE7 and Java 8 SE. The WildFly integration brings experimental Java 9 support, too. It also supports current development snapshots of Java 9, which is expected for release this fall.
The JBOSS EAP 7 release is available for download from JBoss.org.
Continue reading “Five features of JBoss EAP that help you get production ready”
In this blog series we will present several ways to deploy an application on an EAP Domain. The series consists of five parts. Each one will be a standalone article, but the series as a whole will present a range of useful topics for working with JBoss EAP. In the part one, we set up a simple EAP domain with the following topology:
Continue reading JBoss EAP 7 Domain deployments – Part 3: Domain deployment with Common Language Interface CLI.
Messaging is a critical aspect of integrating systems, and while there are many different messaging platforms and infrastructures, a common request is for “zero loss of messages.” From there, the terms “Persistence” and “Durability” often get thrown around, but what do those two things really mean?
Continue reading Persistence vs. Durability in Messaging. Do you know the difference?