Java generics is a great feature that allows you to have compile time checks for generics. However, due to historical reasons of backward compatibility, type information for generics is erased at runtime. A lot of the time this shouldn’t be of much concern. But there are a few cases where type information is needed at runtime for some kind of decision. 

One such situation is in Jakarta REST when the jakarta.ws.rs.core.Response object is used to return a generic collection of a specific type. For example the code below shows the creation and return of a Response object that has a list of HelloEntity as the return payload to the client. 

The Jakarta EE Platform has come a long way since its debut as J2EE back the days of Sun Microsystems. Over the years, it has had its fair share of challenges. A natural consequence of this is that some notions about the platform arising from some of the past challenges that may have been true about past iterations have stuck. This blog post aims to dispel some of these deeply rooted misconceptions about the Jakarta EE Platform, especially after the last major release.

The JakartaOne Livestream is a huge event in the Jakarta EE and MicroProfile calendar. Organised by the Eclipse Foundation, it is a one-day virtual conference for developers and technical business leaders.

It brings insight into the current state and future of Jakarta EE and related technologies focused on developing cloud-native Java applications. 

In regular webinars, our CEO and Founder Steve Millidge provides an update on the progress of Payara Platform: what we've achieved in relation to our yearly roadmaps, and what we have left to do! 

In this webinar, Steve looked at what we've achieved so far in 2021, and ahead to the final quarter of this year and plans for early 2022.

Ever wondered about all the names involved with running Java web applications? Web Server, Application Server, Application Runtime and so on? 

In this guide, we dive a bit deeper in to the terms to help elimate some of the confusion! 

Adam Bien explored the possibilities of Payara Cloud in his recent talk for the 2021 J4K conference! 

He used the Payara Cloud demonstration environment - with the caveat that the user interface is not completed yet - to demonstrate how our next generation application server creates a "serverless" environment; moving the "plumbing behind the scenes" so you only have to worry about selecting your WAR, clicking deploy, and running it on the cloud! 

JDK 17, the next Long-Term Release of Java SE, launched in September. You may have seen many of the great blogs, articles, and videos about what this means for Java developers. For just a few places to start, we like: theJetBrainsteam'sdiscussion on migrating to JDK 17; Todd Ginsberg onhis ten favourite features; andGunter Rotsaert mapping out thedifferences between Java 11 and Java 17. 

But what does the new release mean forJakarta EEdevelopers specifically? If you are using these enterprise-orientated specifications, stewarded by theEclipse Foundation, should you make the switch?

Payara's Rudy De Busscherthinks you should, and explained why in his talk toIstanbul JUG, powered byHazelcast.

Jakarta EE, previously Java EE, is a set of specifications that enables the world wide community of Java developers to work on cloud native Java enterprise applications. It is an open source project maintained by theEclipse Foundation.

Jakarta Concurrency is a small, but fundamental, specification under the Jakarta EE umbrella. As project lead, I provide more information on what it is, its future and how to be involved.