Posts tagged getting started with Jakarta EE
With Jakarta Faces, you can build user interfaces for web applications, including UI components, state management, event handing, input validation, page navigation, and support for internationalization and accessibility. It is a server-side framework that allows for rapid development of web applications, mainly administrative applications which are data entry and business logic heavy. The web pages are created by defining the components that are required and the events that are triggered by the user, and the rendering happens in a separate phase that can be customised to your needs.
In this blog, we mention a few features of Jakarta Faces 3.0 as it is one of the largest specifications of Jakarta EE 9.
With the Jakarta Persistence API, the system can perform the serialization of Java Objects into the Database or read data into objects. You can use Jakarta JPA to read and write Java instances easily from and to the database.
With the help of annotations on Java classes and instance variables, the mapping is defined between the Java world and the database world.
In this blog, we cover some of the basic aspects of the JPA specification and how you can use it. The specification is rather large so make sure you also consult some documentation and other resources to find out all the capabilities of the specification.
Jakarta EE 9.1 was officially released at the end of May 2021. The objective of Jakarta EE 9.1 is to provide certification on Java SE 11 and not to deliver new features. These are scheduled for Jakarta EE 10.
In this blog, we describe how you can use Jakarta EE 9.1 and some background around Jakarta EE 9.1.
Last week, we announced our exciting new webinar series, 'Dismiss the Myths: Get to Know Jakarta EE (Java EE). This is a series of 6 webinars, every Wednesday at 3.00pm BST for the next 6 weeks - with the first one taking place this Wednesday!
Our CEO and FounderSteve Millidge is leading this series, taking one common misconception about Jakarta EE ( previously Java EE ) at a time. Turns out, you might be wrong in thinking Java is behind the times...
This is also the perfect webinar series if you have heard Jakarta EE or Java EE mentioned but aren't sure what it is, what the namespace change means or where its future lies. Steve will be catering to users who are new to the technology as well as long-time Jakarta EE developers.
In this series about getting started with Jakarta EE 9, we look at various specifications and how you can use them for your next application. In the previous blogs of this series, we set up our development environment and had a closer look at implementing REST endpoints.
This time, I will explain a few features of Context and Dependency Injection (CDI). The CDI specification is an important backbone of Jakarta EE as it brings several specifications together. Over the years, it became more and more important as an increasing number of specifications started using CDI as the basis for it.
In this blog, I will tell a bit about the different scopes, the interceptor mechanism, and the Event system.
In this second blog of the "Getting Started with Jakarta EE 9" series, we show you some basic scenarios using the REST specification. Although most people are using the term REST or RESTful API just to indicate they do data transfer over HTTP, and ignore the "Hypermedia as the engine of application State (HATEOS)" part of REST. The technology is used a lot lately to connect the front-end with the back-end.
For those who are not familiar with Jakarta EE, this blog should give you an indication how to create such a REST API with Jakarta EE 9.
The release of Jakarta EE 9, at the end of 2020, was in many ways a historic event. The Java Enterprise framework is already 20 years old, having its first release in 1999. It has changed names a few times but the main concepts of the first release can still be found in this new release. During all those years, it has adapted itself to keep it up to date but has always adhered to its main principle of stability and backward compatibility.