Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Jakarta EE Application Development

You're reading from   Jakarta EE Application Development Build enterprise applications with Jakarta CDI, RESTful web services, JSON Binding, persistence, and security

Arrow left icon
Product type Paperback
Published in Feb 2024
Publisher Packt
ISBN-13 9781835085264
Length 316 pages
Edition 2nd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
David R. Heffelfinger David R. Heffelfinger
Author Profile Icon David R. Heffelfinger
David R. Heffelfinger
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Chapter 1: Introduction to Jakarta EE FREE CHAPTER 2. Chapter 2: Contexts and Dependency Injection 3. Chapter 3: Jakarta RESTful Web Services 4. Chapter 4: JSON Processing and JSON Binding 5. Chapter 5: Microservices Development with Jakarta EE 6. Chapter 6: Jakarta Faces 7. Chapter 7: Additional Jakarta Faces Features 8. Chapter 8: Object Relational Mapping with Jakarta Persistence 9. Chapter 9: WebSockets 10. Chapter 10: Securing Jakarta EE Applications 11. Chapter 11: Servlet Development and Deployment 12. Chapter 12: Jakarta Enterprise Beans 13. Chapter 13: Jakarta Messaging 14. Chapter 14: Web Services with Jakarta XML Web Services 15. Chapter 15: Putting it All Together 16. Index 17. Other Books You May Enjoy

Pluggability

When the original servlet API was released back in the late 1990s, writing servlets was the only way of writing server-side web applications in Java. Since then, several Jakarta EE and third-party frameworks have been built on top of the Servlet API. Examples of such frameworks include JSP and JSF, Apache Struts, Apache Wicket, Spring Web MVC, and several others.

Nowadays, very few (if any) Java web applications are built using the Servlet API directly. Instead, the vast majority of projects utilize one of the available Java web application frameworks. All of these frameworks use the servlet API “under the covers,” therefore setting up an application to use one of these frameworks has always involved making some configuration in the application’s web.xml deployment descriptor. In some cases, some applications use more than one framework. This tends to make the web.xml deployment descriptor fairly large and hard to maintain.

Servlet 3.0 introduced...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image