Skip to content

Commit 35be831

Browse files
Expand Java-related acronyms in documentation
1 parent 5576439 commit 35be831

File tree

1 file changed

+26
-4
lines changed

1 file changed

+26
-4
lines changed

articles/app-service/getting-started.md

Lines changed: 26 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,16 +34,38 @@ Use the following resources to get started with .NET.
3434

3535
## Java
3636

37-
App Service aims to provide robust support for Java. To cover the depth and breadth of Java applications, App Service supports the Java Standard Edition (Java SE), Tomcat, and JBoss Enterprise Application Platform (JBoss EAP) technology stacks. At the base of these stacks, App Service supports all recent Java LTS versions. There are several key scenarios for which you should consider adopting App Service for your Java applications.
37+
App Service aims to provide robust support for Java. To cover the depth and breadth of
38+
Java applications, App Service supports the Java Standard Edition (SE), Tomcat, and
39+
JBoss Enterprise Application Platform (EAP) technology stacks. At the base of these
40+
stacks, App Service supports all recent Java long-term support (LTS) versions. There are
41+
several key scenarios for which you should consider adopting App Service for your Java
42+
applications.
3843

3944
### Java SE on App Service
40-
Java SE on App Service allows you to effortlessly deploy your applications to fully managed JVM instances. You should consider this stack if you have Spring Boot and Quarkus web applications. However, you can use this stack for any application that can be started directly from a JVM and includes an embedded HTTP server. You can simply deploy your JAR file and let App Service do the rest.
45+
Java SE on App Service allows you to effortlessly deploy your applications to fully
46+
managed Java Virtual Machine (JVM) instances. You should consider this stack if you
47+
have Spring Boot and Quarkus web applications. However, you can use this stack for any
48+
application that can be started directly from a JVM and includes an embedded
49+
HyperText Transfer Protocol (HTTP) server. You can simply deploy your
50+
Java archive (JAR) file and let App Service do the rest.
4151

4252
### Tomcat on App Service
43-
This App Service stack supports all recent major and minor versions of Tomcat. You should consider migrating on-premises Tomcat web applications to App Service using this stack. Such applications often use technologies such as the Spring Framework and Hibernate. The stack is also suitable for applications currently running on servers such as WebLogic or WebSphere that can be easily migrated to Tomcat. You can simply deploy your WAR file and let App Service do the rest.
53+
This App Service stack supports all recent major and minor versions of Tomcat.
54+
You should consider migrating on-premises Tomcat web applications to App Service using
55+
this stack. Such applications often use technologies such as the Spring Framework and
56+
Hibernate. The stack is also suitable for applications currently running on servers such
57+
as WebLogic or WebSphere that can be easily migrated to Tomcat. You can simply deploy
58+
your web application achive (WAR) file and let App Service do the rest.
4459

4560
### JBoss EAP on App Service
46-
You can effortlessly run any JBoss EAP version currently supported by Red Hat on this App Service stack. JBoss EAP is fully compatible with the Java EE and Jakarta EE standards. The stack can optionally support any application that requires JBoss EAP clustering. You should consider migrating applications currently running on-premises on JBoss EAP and WildFly to this stack. The stack is also suitable for applications running on servers such as WebLogic or WebSphere that can be easily migrated to JBoss EAP. You can simply deploy your WAR or EAR file and let App Service do the rest.
61+
You can effortlessly run any JBoss EAP version currently supported by Red Hat on this
62+
App Service stack. JBoss EAP is fully compatible with the Java Enterprise Edition (EE)
63+
and Jakarta EE standards. The stack can optionally support any application that requires
64+
JBoss EAP clustering. You should consider migrating applications currently running
65+
on-premises on JBoss EAP and WildFly to this stack. The stack is also suitable for
66+
applications running on servers such as WebLogic or WebSphere that can be easily migrated
67+
to JBoss EAP. You can simply deploy your web application archive (WAR) or
68+
enterprise archive (EAR) file and let App Service do the rest.
4769

4870
Use the following resources to get started with Java.
4971

0 commit comments

Comments
 (0)