Differences

This shows you the differences between two versions of the page.

--- jakarta-ee:web-servers [2023/09/29 14:35] – odefta
+++ jakarta-ee:web-servers [2025/01/02 18:22] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Web Servers Compatible With Jakarta EE / Java EE ======
+===== Apache Tomcat =====
+<note>Tomcat is technically a servlet container, but it's widely used for serving Java EE web applications. It doesn't support the full Java EE stack out of the box but can be used with additional libraries and frameworks.</note>
+===== WildFly=====
-  - **Apache Tomcat**
+Formerly known as JBoss AS, developed by Red Hat, it's a fully compliant Java EE and Jakarta EE application server and is widely used in the enterprise environment.
-   <note>Tomcat is technically a servlet container, but it's widely used for serving Java EE web applications. It doesn't support the full Java EE stack out of the box but can be used with additional libraries and frameworks.</note>
-  - **WildFly**
+===== IBM WebSphere=====
-    Formerly known as JBoss AS, developed by Red Hat, it's a fully compliant Java EE and Jakarta EE application server and is widely used in the enterprise environment.
-  - **IBM WebSphere**
+A fully compliant Java EE and Jakarta EE application server developed by IBM, known for its enterprise features and support.
-    A fully compliant Java EE and Jakarta EE application server developed by IBM, known for its enterprise features and support.
-  - **Oracle WebLogic**
+=====  Oracle WebLogic =====
-    Oracle’s own application server, fully compliant with Java EE, known for its robustness, scalability, and enterprise-grade features.
-  - **Payara Server**
+Oracle’s own application server, fully compliant with Java EE, known for its robustness, scalability, and enterprise-grade features.
-    Derived from GlassFish, Payara is an open-source application server that offers support for both Java EE and Jakarta EE and is designed for production environments.
-  - **GlassFish**
+===== Payara Server =====
-    Originally developed by Sun Microsystems, GlassFish was the reference implementation for Java EE, but it's not as actively developed since Payara forked from it.
-  - **OpenLiberty**
+Derived from GlassFish, Payara is an open-source application server that offers support for both Java EE and Jakarta EE and is designed for production environments.
-    Developed by IBM, OpenLiberty is a lightweight, modular, and cloud-native focused server, supporting both Java EE and Jakarta EE.
-  - **TomEE**
+===== GlassFish =====
-    Apache TomEE is a Java EE and Jakarta EE compliant version of Apache Tomcat, including additional libraries to support the full Java EE stack.
-  - **Jetty**
+Originally developed by Sun Microsystems, GlassFish was the reference implementation for Java EE, but it's not as actively developed since Payara forked from it.
-    <note> Like Tomcat, Jetty is technically a servlet container. It can be used for serving Java EE web applications with additional libraries.</note>
-  - **Piranha**
+===== OpenLiberty =====
-    Piranha is a newer, cloud-native, and lightweight application server with support for Jakarta EE.
+Developed by IBM, OpenLiberty is a lightweight, modular, and cloud-native focused server, supporting both Java EE and Jakarta EE.
+===== TomEE =====
+Apache TomEE is a Java EE and Jakarta EE compliant version of Apache Tomcat, including additional libraries to support the full Java EE stack.
+===== Jetty =====
+<note> Like Tomcat, Jetty is technically a servlet container. It can be used for serving Java EE web applications with additional libraries.
+</note>
+===== Piranha =====
+Piranha is a newer, cloud-native, and lightweight application server with support for Jakarta EE.