Chapter 1. Get Started Developing Applications 1.1. About Jakarta EE 1.1.1. Jakarta EE 8 JBoss EAP 7 is a Jakarta EE 8-compatible implementation for both Jakarta EE Web Profile and Jakarta EE Platform specifications. For information about Jakarta EE 8, see About Jakarta EE . 1.1.2. Overview of Jakarta EE Profiles Jakarta EE defines different profiles. Each profile is a subset of APIs that represent configurations that are suited to specific classes of applications. Jakarta EE 8 defines specifications for the Web Profile and the Platform profiles. A product can choose to implement the Platform, the Web Profile, or one or more custom profiles, in any combination. Jakarta EE Web Profile includes a selected subset of APIs that are designed to be useful for web application development. Jakarta EE Platform profile includes the APIs defined by the Jakarta EE 8 Web Profile, plus the complete set of Jakarta EE 8 APIs that are useful for enterprise application development. JBoss EAP 7.4 is a Jakarta EE 8 compatible implementation for Web Profile and Full Platform specifications. See Jakarta EE Specifications for the complete list of Jakarta EE 8 APIs. 1.2. Setting Up the Development Environment Download and install Red Hat CodeReady Studio. For instructions, see Installing CodeReady Studio stand-alone using the Installer in the Red Hat CodeReady Studio Installation Guide . Set up the JBoss EAP server in Red Hat CodeReady Studio. For instructions, see Downloading, Installing, and Setting Up JBoss EAP from within the IDE in the Getting Started with CodeReady Studio Tools guide. 1.3. Configure Annotation Processing in Red Hat CodeReady Studio Annotation Processing (AP) is turned off by default in Eclipse. If your project generates implementation classes, this can result in java.lang.ExceptionInInitializerError exceptions, followed by CLASS_NAME (implementation not found) error messages when you deploy your project. You can resolve these issues in one of the following ways. You can enable annotation processing for the individual project or you can enable annotation processing globally for all Red Hat CodeReady Studio projects . Enable Annotation Processing for an Individual Project To enable annotation processing for a specific project, you must add the m2e.apt.activation property with a value of jdt_apt to the project's pom.xml file. <properties> <m2e.apt.activation>jdt_apt</m2e.apt.activation> </properties> You can find examples of this technique in the pom.xml files for the logging-tools and kitchensink-ml quickstarts that ship with JBoss EAP. Enable Annotation Processing Globally in Red Hat CodeReady Studio Select Window Preferences . Expand Maven , and select Annotation Processing . Under Select Annotation Processing Mode , select Automatically configure JDT APT (builds faster , but outcome may differ from Maven builds) , then click Apply and Close . 1.4. Configure the Default Welcome Web Application JBoss EAP includes a default Welcome application, which displays at the root context on port 8080 by default. This default Welcome application can be replaced with your own web application. This can be configured in one of two ways: Change the welcome-content file handler Change the default-web-module You can also disable the welcome content . Change the welcome-content File Handler Modify the existing welcome-content file handler's path to point to the new deployment. Note Alternatively, you could create a different file handler to be used by the server's root. Reload the server for the changes to take effect. Change the default-web-module Map a deployed web application to the server's root. Reload the server for the changes to take effect. Disable the Default Welcome Web Application Disable the welcome application by removing the location entry / for the default-host . Reload the server for the changes to take effect.

Commands:
<properties> <m2e.apt.activation>jdt_apt</m2e.apt.activation> </properties>
/subsystem=undertow/configuration=handler/file=welcome-content:write-attribute(name=path,value=" /path/to/content ")
/subsystem=undertow/configuration=handler/file= NEW_FILE_HANDLER :add(path=" /path/to/content ") /subsystem=undertow/server=default-server/host=default-host/location=\/:write-attribute(name=handler,value= NEW_FILE_HANDLER )
reload
/subsystem=undertow/server=default-server/host=default-host:write-attribute(name=default-web-module,value=hello.war)
reload
/subsystem=undertow/server=default-server/host=default-host/location=\/:remove
reload