Chapter 1. Get Started Developing Applications

1. Log in to the Red Hat Customer Portal.
2. Click Downloads.
3. In the Product Downloads list, click Red Hat JBoss Enterprise Application Platform.
4. Select the desired version in the Version drop-down menu.
5. Find the Red Hat JBoss Enterprise Application Platform 7.0.0 Quickstarts entry in the table and click Download.
6. Save the ZIP file to the desired directory.
7. Extract the ZIP file.

1. Start JBoss Developer Studio.
2. Select File Import.

3. Choose Maven Existing Maven Projects, then click Next.

   Figure 1.7. Import Existing Maven Projects

   

   View larger image

   

4. Browse to the desired quickstart’s directory (for example the helloworld quickstart), and click OK. The Projects list box is populated with the pom.xml file of the selected quickstart project.

   Figure 1.8. Select Maven Projects

   

   View larger image

   
5. Click Finish.

1. If you have not yet defined a server, add the JBoss EAP server to JBoss Developer Studio.

2. Right-click the jboss-helloworld project in the Project Explorer tab and select Run As Run on Server.

   Figure 1.9. Run As - Run on Server

   

   View larger image

   

3. Select JBoss EAP 7.0 from the server list and click Next.

   Figure 1.10. Run on Server

   

   View larger image

   

4. The jboss-helloworld quickstart is already listed to be configured on the server. Click Finish to deploy the quickstart.

   Figure 1.11. Modify Resources Configured on the Server

   

   View larger image

   

5. Verify the results.

   • In the Server tab, the JBoss EAP 7.0 server status changes to Started .

   • The Console tab shows messages detailing the JBoss EAP server start and the helloworld quickstart deployment.

     WFLYUT0021: Registered web context: /jboss-helloworld
     WFLYSRV0010: Deployed "jboss-helloworld.war" (runtime-name : "jboss-helloworld.war")

     Copy to Clipboard Toggle word wrap
   • The helloworld application is available at http://localhost:8080/jboss-helloworld and displays the text Hello World!.

1. Import the bean-validation quickstart into JBoss Developer Studio.
2. In the Servers tab, right-click on the server and choose Start to start the JBoss EAP server. If you do not see a Servers tab or have not yet defined a server, add the JBoss EAP server to Red Hat JBoss Developer Studio.
3. Right-click on the jboss-bean-validation project in the Project Explorer tab and select Run As Maven Build.

4. Enter the following in the Goals input field and then click Run.

   clean test -Parq-wildfly-remote

   Copy to Clipboard Toggle word wrap

   Figure 1.12. Edit Configuration

   

   View larger image

   

5. Verify the results.

   The Console tab shows the results of the bean-validation Arquillian tests:

   -------------------------------------------------------
    T E S T S
   -------------------------------------------------------
   Running org.jboss.as.quickstarts.bean_validation.test.MemberValidationTest
   Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.189 sec
   
   Results :
   
   Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
   
   [INFO] ------------------------------------------------------------------------
   [INFO] BUILD SUCCESS
   [INFO] ------------------------------------------------------------------------

   Copy to Clipboard Toggle word wrap

Run the helloworld Quickstart from the Command Line

1. Review the README.md file in the root directory of the helloworld quickstart.

2. Start the JBoss EAP server.

   $ EAP_HOME/bin/standalone.sh

   Copy to Clipboard Toggle word wrap
3. Navigate to the helloworld quickstart directory.

4. Build and deploy the quickstart using the Maven command provided in the quickstart’s README.md file.

   mvn clean install wildfly:deploy

   Copy to Clipboard Toggle word wrap
5. The helloworld application is now available at http://localhost:8080/jboss-helloworld and displays the text Hello World!.

1. Review the HelloWorldServlet code.

   The HelloWorldServlet.java file is located in the src/main/java/org/jboss/as/quickstarts/helloworld/ directory. This servlet sends the information to the browser.

   HelloWorldServlet Class Code Example

   42 @SuppressWarnings("serial")
   43 @WebServlet("/HelloWorld")
   44 public class HelloWorldServlet extends HttpServlet {
   45
   46     static String PAGE_HEADER = "<html><head><title>helloworld</title></head><body>";
   47
   48     static String PAGE_FOOTER = "</body></html>";
   49
   50     @Inject
   51	   HelloService helloService;
   52
   53     @Override
   54     protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
   55         resp.setContentType("text/html");
   56         PrintWriter writer = resp.getWriter();
   57         writer.println(PAGE_HEADER);
   58         writer.println("<h1>" + helloService.createHelloMessage("World") + "</h1>");
   59         writer.println(PAGE_FOOTER);
   60         writer.close();
   61     }
   62
   63 }

   Copy to Clipboard Toggle word wrap

   Expand

   Table 1.1. HelloWorldServlet Details

   Line	Note
   43	All you need to do is add the @WebServlet annotation and provide a mapping to a URL used to access the servlet.
   46-48	Every web page needs correctly formed HTML. This quickstart uses static Strings to write the minimum header and footer output.
   50-51	These lines inject the HelloService CDI bean which generates the actual message. As long as we don’t alter the API of HelloService, this approach allows us to alter the implementation of HelloService at a later date without changing the view layer.
   58	This line calls into the service to generate the message "Hello World", and write it out to the HTTP request.

   Show more

2. Review the HelloService code.

   The HelloService.java file is located in the src/main/java/org/jboss/as/quickstarts/helloworld/ directory. This service simply returns a message. No XML or annotation registration is required.

   HelloService Class Code Example

   public class HelloService {
   
       String createHelloMessage(String name) {
           return "Hello " + name + "!";
       }
   }

   Copy to Clipboard Toggle word wrap

1. Examine the faces-config.xml file.

   This quickstart uses the JSF 2.2 version of faces-config.xml filename. A standardized version of Facelets is the default view handler in JSF 2.2 so it requires no configuration. This file consists of only the root element and is simply a marker file to indicate JSF should be enabled in the application.

   <faces-config version="2.2"
      xmlns="http://xmlns.jcp.org/xml/ns/javaee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="
         http://xmlns.jcp.org/xml/ns/javaee
         http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd">
   
   </faces-config>

   Copy to Clipboard Toggle word wrap

2. Examine the beans.xml file.

   The beans.xml file contains a version number of 1.1 and a bean-discovery-mode of all. This file is a marker file that identifies the WAR as a bean archive and tells JBoss EAP to look for beans in this application and to activate the CDI.

   <beans xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
         http://xmlns.jcp.org/xml/ns/javaee
         http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd"
       bean-discovery-mode="all">
   </beans>

   Copy to Clipboard Toggle word wrap