We need to download and install the following software:

Set the environment variables: JAVA_HOME, JBOSS_HOME, MAVEN_HOME, and MYSQL_HOME. Add %JAVA_HOME%/bin, %MAVEN_HOME%/bin, %JBOSS_HOME%/bin, and %MYSQL_HOME%/bin to the PATH environment variable. The environment settings used are C:\wildfly-8.1.0.Final for JBOSS_HOME, C:\Program Files\MySQL\MySQL Server 5.6.21 for MYSQL_HOME, C:\maven\apache-maven-3.0.5 for MAVEN_HOME, and C:\Program Files\Java\jdk1.7.0_51 for JAVA_HOME. Run the add-user.bat script from the %JBOSS_HOME%/bin directory to create a user for the WildFly administrator console. When prompted What type of user do you wish to add?, select a) Management User. The other option is b) Application User.

Management User is used to log in to Administration Console, and Application User is used to access applications. Subsequently, specify the Username and Password for the new user. When prompted with the question, Is this user going to be used for one AS process to connect to another AS..?, enter the answer as no. When installing and configuring the MySQL database, specify a password for the root user (the password mysql is used in the sample application).

As the application is run on WildFly 8.1, we need to create a runtime environment for WildFly 8.1 in Eclipse. Select Window | Preferences in Eclipse. In Preferences, select Server | Runtime Environment. Click on the Add button to add a new runtime environment, as shown in the following screenshot:

In New Server Runtime Environment, select JBoss Community | WildFly 8.x Runtime. Click on Next:

In WildFly Application Server 8.x, which appears below New Server Runtime Environment, specify a Name for the new runtime or choose the default name, which is WildFly 8.x Runtime. Select the Home Directory for the WildFly 8.x server using the Browse button. The Home Directory is the directory where WildFly 8.1 is installed. The default path is C:\wildfly-8.1.0.Final for this chapter and subsequent chapters. Select the Runtime JRE as JavaSE-1.7. If the JDK location is not added to the runtime list, first add it from the JRE preferences screen in Eclipse. In Configuration base directory, select standalone as the default setting. In Configuration file, select standalone.xml as the default setting. Click on Finish:

A new server runtime environment for WildFly 8.x Runtime gets created, as shown in the following screenshot. Click on OK:

Creating a Server Runtime Environment for WildFly 8.x is not a prerequisite for creating a Java EE project in Eclipse. In the next section, we will create a new Java EE project for an EJB 3.x application.

JBoss Tools provides project templates for different types of JBoss projects. In this section, we will create a Java EE project for an EJB 3.x application. Select File | New | Other in Eclipse IDE. In the New wizard, select the JBoss Central | Java EE EAR Project wizard. Click on the Next button:

The Java EE EAR Project wizard gets started. By default, a Java EE 6 project is created. A Java EE EAR Project is a Maven project. The New Project Example window lists the requirements and runs a test for the requirements. The JBoss AS runtime is required and some plugins (including the JBoss Maven Tools plugin) are required for a Java EE project. Select Target Runtime as WildFly 8.x Runtime, which was created in the preceding section. Then, check the Create a blank project checkbox. Click on the Next button:

Specify Project name as jboss-ejb3, Package as org.jboss.ejb3, and tick the Use default Workspace location box. Click on the Next button:

Specify Group Id as org.jboss.ejb3, Artifact Id as jboss-ejb3, Version as 1.0.0, and Package as org.jboss.ejb3.model. Click on Finish:

A Java EE project gets created, as shown in the following Project Explorer window. Delete the jboss-ejb3/jboss-ejb3-ear/src/main/application/META-INF/jboss-ejb3-ds.xml configuration file. The jboss-ejb3 project consists of three subprojects: jboss-ejb3-ear, jboss-ejb3-ejb, and jboss-ejb3-web. Each subproject consists of a pom.xml file for Maven. Initially the subprojects indicate errors with red error markers, but these would get fixed when the main project is built later in the chapter. Initially the subprojects might indicate errors with red error markers, but these would get fixed when the main project is built later in the chapter. We will configure a data source with the MySQL database in a later section. The jboss-ejb3-ejb subproject consists of a META-INF/persistence.xml file within the src/main/resources source folder for the JPA database persistence configuration.

We will use MySQL as the database for data for the EJB application. In the next section, we will create a data source in the MySQL database.

The default data source in WildFly 8.1 is configured with the H2 database engine. There are several options available for a database. The top four most commonly used relational databases are Oracle database, MySQL database, SQL Server, and PostgreSQL Server. Oracle database and SQL Server are designed for enterprise level applications and are not open source. Oracle database offers more features to facilitate system and data maintenance. It also offers features to prevent system and data failure as compared to SQL Server. MySQL and PostgreSQL are open source databases with comparable features and designed primarily for small scale applications. We will use MySQL database. Some of the reasons to choose MySQL are discussed at http://www.mysql.com/why-mysql/topreasons.html.

We will configure a datasource with the MySQL database for use in the EJB 3.x application for object/relational mapping. Use the following steps to configure a datasource:

In the next section, we will create entities for the EJB 3.x application.

In EJB 3.x, an entity is a POJO (Plain Old Java Object) persistent domain object that represents a database table row. As an entity is a Java class, create a Java class in the jboss-ejb3-ejb subproject of the jboss-ejb3 project. Select File | New. In the New window, select Java | Class and click on Next:

Select/specify jboss-ejb3/jboss-ejb3-ejb/src/main/java as the Java Source folder, org.jboss.ejb3.model as the Package, and Catalog as the class Name. Click on Finish:

Similarly, add Java classes for the Edition.java, Section.java, and Article.java entities, as shown in the following Project Explorer:

Next, we develop the EJB 3.x entities. A JPA persistence provider is required for the EJB entities, and we will use the Hibernate persistence provider. The Hibernate persistence provider has some peculiarities that need to be mentioned, as follows:

We will develop the Catalog, Edition, Section, and Article class with one-to-many relationship between the Catalog and Edition class, the Edition and Section class, and the Section and Article class, as shown in the following UML class diagram:

Annotate the Catalog entity class with the @Entity annotation and the @Table annotation. If the @Table annotation is not used, then the entity name is used as the table name by default. In the @Table annotation, specify the table name as CATALOG and uniqueConstraints, using the @UniqueConstraint annotation for the id column. Specify the named queries as findCatalogAll, which selects all Catalog and findCatalogByJournal entities. This selects a Catalog entity by Journal, using the @NamedQueries and @NamedQuery annotations:

@Entity
@Table(name = "CATALOG", uniqueConstraints = @UniqueConstraint(columnNames = "ID"))
@NamedQueries({
  @NamedQuery(name="findCatalogAll", query="SELECT c FROM Catalog c"),
  @NamedQuery(name="findCatalogByJournal", 
    query="SELECT c FROM Catalog c WHERE c.journal = :journal")
})
public class Catalog implements Serializable {
}

Specify the no-argument constructor, which is required in an entity class. The Catalog entity class implements the Serializable interface to serialize a cache-enabled entity to a cache when persisted to a database. To associate a version number with a serializable class for a serialization runtime, specify a serialVersionUID variable. Declare String variables for id and journal bean properties and for a collection of Set<Edition> type, as the Catalog entity has a bi-directional one-to-many association to Edition. The collection is chosen as Set for the reason mentioned earlier. Hibernate does not support more than one EAGER association of the java.util.List type. Add get/set methods for the bean properties. The @Id annotation specifies the identifier property. The @Column annotation specifies the column name associated with the property. The nullable element is set to false as the primary key cannot be null.

Specify the bi-directional one-to-many association to Edition using the @OneToMany annotation. The mappedBy element is specified on the non-owning side of the relationship, which is the Catalog entity. The cascade element is set to ALL. Cascading is used to cascade database table operations to associated tables. The fetch element is set to EAGER. With EAGER fetching the associated entity, collection is immediately fetched when an entity is retrieved:

// bi-directional many-to-one association to Edition
@OneToMany(mappedBy = "catalog", targetEntity=org.jboss.ejb3.model.Edition.class, cascade = { CascadeType.ALL }, fetch = FetchType.EAGER)
  public Set<Edition> getEditions() {
    return this.editions;
  }
}

As mentioned earlier, associations marked with mappedBy must not specify @JoinTable or @JoinColumn. The get and set methods for the Edition collection are also specified. The Catalog.java entity class is available in the code download for the chapter at http://www.packtpub.com/support.

Next, develop the entity class for the EDITION database table: Edition.java. Specify the @Entity, @Table, @Id , @Column, and @GeneratedValue annotations, as discussed for the Catalog entity. Specify the findEditionAll and findEditionByEdition named queries to find Edition collections. Specify the bean properties and associated get/set methods for id and edition. Also, specify the one-to-many association to the Section entity using a collection of the Set type. The bi-directional many-to-one association to the Catalog relationship is specified using the @ManyToOne annotation, and with cascade of type PERSIST, MERGE, and REFRESH. The Edition entity is the owning side of the relationship. Using the @JoinTable annotation, a join table is included on the owning side to initiate cascade operations. The join columns are specified using the @JoinColumn annotation. The Edition.java entity class is available in the code download for the chapter.

Develop the entity class for the SECTION table: Section.java. Specify the findSectionAll and findSectionBySectionName named queries to find Section entities. Specify the id and sectionname bean properties. Specify the bi-directional many-to-one association to Edition using the @ManyToOne annotation and the bi-directional one-to-many association to Article using @OneToMany. The @JoinTable and @JoinColumn are specified only for the @ManyToOne association for which Section is the owning side. The Section.java entity class is available in the code download for the chapter.

Specify the entity class for the ARTICLE table: Article.java. The Article entity is mapped to the ARTICLE database table using the @TABLE annotation. Add the findArticleAll and findArticleByTitle named queries to find Article entities. Specify id and sectionname bean properties and the associated get/set methods. The Article entity is the owning side of the bi-directional many-to-one association to Section. Therefore, the @JoinTable and @JoinColumn are specified. The Article.java class is available in the code downloaded for the chapter.

The META-INF/persistence.xml configuration file in the ejb/src/main/resources folder in the jboss-ejb3-ejb subproject was created when we created the Java EE project. The persistence.xml specifies a persistence provider to be used to map object/relational entities to the database. Specify that, the persistence unit is using the persistence-unit element. Set the transaction-type to JTA (the default value). Specify the persistence provider as the Hibernate persistence provider: org.hibernate.ejb.HibernatePersistence. Set the jta-data-source element value to the java:jboss/datasources/MySQLDS data source, which we created earlier. Specify the entity classes using the class element. The DDL generation strategy is set to create-drop using the hibernate.hbm2ddl.auto property, which automatically validates or exports the DDL schema to the database, when the SessionFactory class is created. With the create-drop strategy, the required tables are created and dropped when the SessionFactory is closed. The hibernate.show_sql property is set to false. Setting it to true implies that all SQL statements be the output, which is an alternative method to debug. The hibernate.dialect property is set to org.hibernate.dialect.MySQLDialect for MySQL Database. Other Hibernate properties (http://docs.jboss.org/hibernate/orm/3.3/reference/en/html/session-configuration.html) can also be specified as required. The persistence.xml configuration file is listed in the following code:

<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0" xsi:schemaLocation="         http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
  <persistence-unit name="em" transaction-type="JTA">
    <provider>org.hibernate.ejb.HibernatePersistence</provider>
    <!-- If you are running in a production environment, add a managed data source, the example data source is just for development and testing! -->
    <jta-data-source>java:jboss/datasources/MySQLDS</jta-data-source>
    <class>org.jboss.ejb3.model.Article</class>
    <class>org.jboss.ejb3.model.Catalog</class>
    <class>org.jboss.ejb3.model.Edition</class>
    <class>org.jboss.ejb3.model.Section</class>
    <properties>
      <!-- Properties for Hibernate -->
      <property name="hibernate.hbm2ddl.auto" value="create-drop" />
      <property name="hibernate.show_sql" value="false" />
      <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" />
    </properties>
  </persistence-unit>
</persistence>

The JPA specification does not mandate a persistence provider to create tables with the hibernate.hbm2ddl.auto property set to create-drop or create. Hibernate persistence provider supports creating tables. In addition to the entity tables, some additional tables (such as the join tables and the sequence table) are created by the Hibernate persistence provider.

One of the best practices of developing entities for separation of concerns and maintainable code and as a result better performance is to wrap the entities in a session bean facade. With a Session Facade, fewer remote method calls are required, and an outer transaction context is created with which each get method invocation does not start a new transaction. Session Facade is one of the core Java EE design patterns (http://www.oracle.com/technetwork/java/sessionfacade-141285.html). Create a CatalogSessionBeanFacade session bean class in the org.jboss.ejb3.model package, as shown in the following screenshot. The Session Facade class can also be created in a different package (such as org.jboss.ejb3.view):

The session bean class is annotated with the @Stateless annotation:

@Stateless
public class CatalogSessionBeanFacade {}

In the bean session, we use an EntityManager to create, remove, find, and query persistence entity instances. Inject a EntityManager using the @PersistenceContext annotation. Specify the unitName as the unitName configured in persistence.xml. Next, specify the getAllEditions, getAllSections, getAllArticles, getAllCatalogs get methods to fetch the collection of entities. The get methods get all entities' collections with the named queries specified in the entities. The createNamedQuery method of EntityManager is used to create a Query object from a named query. Specify the TransactionAttribute annotation's TransactionAttributeType enumeration to REQUIRES_NEW, which has the advantage that if a transaction is rolled back due to an error in a different transaction context from which the session bean is invoked, it does not affect the session bean.

To demonstrate the use of the entities, create the test data with the createTestData convenience method in the session bean. Alternatively, a unit test or an extension class can also be used. Create a Catalog entity and set the journal using the setJournal method. We do not set the id for the Catalog entity as we use the GenerationType.AUTO generation strategy for the ID column. Persist the entity using the persist method of the EntityManager object. However, the persist method does not persist the entity to the database. It only makes the entity instance managed and adds it to the persistence context. The EntityManager.flush() method is not required to be invoked to synchronize the entity with the database as EntityManager is configured with FlushModeType as AUTO (the other setting being COMMIT) and a flush will be done automatically when the EntityManager.persist() is invoked:

Catalog catalog1 = new Catalog();
catalog1.setJournal("Oracle Magazine");
em.persist(catalog1);

Similarly, create and persist an Edition entity object. Add the Catalog object: catalog1 using the setCatalog method of the Edition entity class:

Edition edition = new Edition();
edition.setEdition("January/February 2009");
edition.setCatalog(catalog1);
em.persist(edition);

Likewise add the Section and Article entity instances. Add another Catalog object, but without any associated Edition, Section, or Article entities:

Catalog catalog2 = new Catalog();
catalog2.setJournal("Linux Magazine");
em.persist(catalog2);

Next, we will delete data with the deleteSomeData method, wherein we first create a Query object using the named query findCatalogByJournal. Specify the journal to delete with the setParameter method of the Query object. Get the List result with the getResultList method of the Query object. Iterate the List result and remove the Catalog objects with the remove method of the EntityManager object. The remove method only removes the Catalog object from the persistence context:

public void deleteSomeData() {
  // remove a catalog
  Query q = em.createNamedQuery("findCatalogByJournal");
  //q.setParameter("journal", "Linux Magazine");
  q.setParameter("journal", "Oracle Magazine");
  List<Catalog> catalogs = q.getResultList();
  for (Catalog catalog : catalogs) {
    em.remove(catalog);
  }
}

The CatalogSessionBeanFacade session bean class is available in the code downloaded for the chapter.

Next, we will create a JSP client to test the EJB entities. We will look up the session bean using a local JNDI name. Subsequently, we will invoke the testData method of the session bean to test database persistence using these entities. First create a JSP file. Select File | New | Other, and in the New wizard, select Web | JSP File and click on Next, as in the following screenshot:

In the New JSP File wizard, select the jboss-ejb3/web/src/main/webapp folder in the jboss-ejb3-web subproject. Specify catalog.jsp as as File name and click on Next. Then click on Finish:

The catalog.jsp file gets added to the jboss-ejb3-web subproject:

We need to retrieve the CatalogSessionBeanFacade component from the JSP client. WildFly 8 provides the local JNDI (Java Naming and Directory Interface) namespace: Java, and the following JNDI contexts:

When the jboss-ejb3 application is deployed, the JNDI bindings in the namespaces (discussed in the preceding table) are created as indicated by the server message:

JNDI bindings for session bean named CatalogSessionBeanFacade in deployment unit subdeployment "jboss-ejb3-ejb.jar" of deployment "jboss-ejb3-ear.ear" are as follows:
  java:global/jboss-ejb3-ear/jboss-ejb3-ejb/CatalogSessionBeanFacade!org.jboss.ejb3.model.CatalogSessionBeanFacade
  java:app/jboss-ejb3-ejb/CatalogSessionBeanFacade!org.jboss.ejb3.model.CatalogSessionBeanFacade
  java:module/CatalogSessionBeanFacade!org.jboss.ejb3.model. CatalogSession
BeanFacade
  java:global/jboss-ejb3-ear/jboss-ejb3-ejb/CatalogSessionBeanFacade
  java:app/jboss-ejb3-ejb/CatalogSessionBeanFacade
  java:module/CatalogSessionBeanFacade

Next we will retrieve the session bean façade: CatalogSessionBeanFacade using the standard Java SE JNDI API, which does not require any additional configuration, using the local JNDI lookup in the java:app namespace. For the local JNDI lookup, we need to create an InitialContext object:

Context context = new InitialContext();

Using the local JNDI name lookup in the java:app namespace, retrieve the CatalogSessionBeanFacade component:

CatalogSessionBeanFacade bean = (CatalogSessionBeanFacade) context .lookup("java:app/jboss-ejb3-ejb/CatalogSessionBeanFacade!org.jboss.ejb3.model.CatalogSessionBeanFacade");

Invoke the createTestData method and retrieve the List Catalog entities. Iterate over the Catalog entities and output the catalog ID as the journal name:

bean.createTestData();
List<Catalog> catalogs = beanRemote.getAllCatalogs();
out.println("<br/>" + "List of Catalogs" + "<br/>");
for (Catalog catalog : catalogs) {
  out.println("Catalog Id:");
  out.println("<br/>" + catalog.getId() + "<br/>");
  out.println("Catalog Journal:");
  out.println(catalog.getJournal() + "<br/>");
}

Similarly, obtain the Entity, Section, and Article entities and output the entity property values. The catalog.jsp file is available in the code downloaded for the chapter.

We will generate an EAR file using the Maven project: jboss-ejb3, which includes the jboss-ejb3-ejb, jboss-ejb-web and jboss-ejb3-ear subproject/artifacts. We will use the Maven build tool to compile, package, and deploy the EAR application. The jboss-ejb3-ear module to be deployed to WildFly has two submodules: jboss-ejb3-web and jboss-ejb3-ejb.

The jboss-ejb3-ear, jboss-ejb3-web and jboss-ejb3-ejb modules may be referred to as ear, web, and ejb modules respectively. The ear module has dependency on the web module, and the web module has dependency on the ejb module, as shown in the following diagram:

The ejb, web, and ear modules can be built and installed individually using subproject-specific pom.xml, or these can be built together using the pom.xml file in the jboss-ejb3 project. If built individually, the ejb module has to be built and installed before the web module, as the web module has a dependency on the ejb module. The ear module is to be built after the web and ejb modules have been built and installed. We will build and install the top level project using the pom.xml file in the jboss-ejb3 project, which has dependency specified on the jboss-ejb3-web and jboss-ejb3-ejb artifacts. The pom.xml file for the jboss-ejb3-ejb subproject specifies packaging as ejb. The WildFly 8.x provides most of the APIs required for an EJB 3.x application. The provided APIs are specified with scope set to provided in pom.xml. Dependencies for the EJB 3.1 API and the JPA 2.0 API are pre-specified. Add the following dependency for the Hibernate Annotations API:

<dependency>
  <groupId>org.jboss.spec.javax.ejb</groupId>
  <artifactId>jboss-ejb-api_3.1_spec</artifactId>
  <version>1.0.0.Final</version>
  <scope>provided</scope>
</dependency>
<dependency>
  <groupId>org.hibernate.javax.persistence</groupId>
  <artifactId>hibernate-jpa-2.0-api</artifactId>
  <version>1.0.0.Final</version>
  <scope>provided</scope>
</dependency>
<dependency>
  <groupId>org.hibernate</groupId>
  <artifactId>hibernate-annotations</artifactId>
  <version>3.5.6-Final</version>
</dependency>

The Hibernate Validator API dependency is also preconfigured in pom.xml. The build is preconfigured with the Maven EJB plugin, which is required to package the subproject into an EJB module. The EJB version in the Maven EJB plugin is 3.1:

<build>
  <finalName>${project.artifactId}</finalName>
  <plugins>
    <plugin>
      <artifactId>maven-ejb-plugin</artifactId>
      <version>${version.ejb.plugin}</version>
      <configuration>
        <!-- Tell Maven we are using EJB 3.1 -->
        <ejbVersion>3.1</ejbVersion>
      </configuration>
    </plugin>
  </plugins>
</build>

The Maven POM.xml file for the EJB subproject is available in the code downloaded for the chapter.

Most of the required configuration for the jboss-ejb3-web subproject is pre-specified. The packaging for the jboss-ejb3-web artifacts is set to war:

<artifactId>jboss-ejb3-web</artifactId>
<packaging>war</packaging>
<name>jboss-ejb3 Web module</name>

The pom.xml file for the subproject pre-specifies most of the required dependencies. It also specifies dependency on the jboss-ejb3-ejb artifact:

<dependency>
  <groupId>org.jboss.ejb3</groupId>
  <artifactId>jboss-ejb3-ejb</artifactId>
  <type>ejb</type>
  <version>1.0.0</version>
  <scope>provided</scope>
</dependency>

The EJB 3.1 API, the JPA 2.0 API, the JSF 2.1 API, and the JAX-RS 1.1 API are provided by the WildFly 8.x server, as indicated by the provided scope in the dependency declarations. Add the dependency on the hibernate-annotations artifact. The build is preconfigured with the Maven WAR plugin, which is required to package the subproject into an WAR file:

<?xml version="1.0" encoding="UTF-8"?>
<build>
  <finalName>${project.artifactId}</finalName>
  <plugins>
    <plugin>
      <artifactId>maven-war-plugin</artifactId>
      <version>${version.war.plugin}</version>
      <configuration>
        <!-- Java EE 6 doesn't require web.xml, Maven needs to catch up! -->
        <failOnMissingWebXml>false</failOnMissingWebXml>
      </configuration>
    </plugin>
  </plugins>
</build>

The pom.xml file for the jboss-ejb3-web subproject is available in the code downloaded for the chapter.

In pom.xml for the jboss-ejb3-ear subproject, the packaging for the jboss-ejb3-ear artifact is specified as ear:

<artifactId>jboss-ejb3-ear</artifactId>
<packaging>ear</packaging>

The pom.xml file specifies dependency on the ejb and web modules:

<dependencies>
  <!-- Depend on the ejb module and war so that we can package them -->
  <dependency>
  <groupId>org.jboss.ejb3</groupId>
  <artifactId>jboss-ejb3-web</artifactId>
  <version>1.0.0</version>
  <type>war</type>
</dependency>
  <dependency>
  <groupId>org.jboss.ejb3</groupId>
  <artifactId>jboss-ejb3-web</artifactId>
  <version>1.0.0</version>
  <type>war</type>
</dependency>
</dependencies>

The build tag in the pom.xml file specifies the configuration for the maven-ear-plugin plugin with output directory as the deployments directory in the WildFly 8.x standalone server. The EAR file generated from the Maven project is deployed to the directory specified in the <outputDirectory/> element. Specify the <outputDirectory/> element as the C:\wildfly-8.1.0.Final\standalone\deployments directory. The outputDirectory might need to be modified based on the installation directory of WildFly 8.1. The EAR, WAR, and JAR modules in the deployments directory get deployed to the WildFly automatically, if the server is running:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-ear-plugin</artifactId>
  <version>2.8</version>
  <configuration>
    <!-- Tell Maven we are using Java EE 6 -->
    <version>6</version>
    <!-- Use Java EE ear libraries as needed. Java EE ear libraries are in easy way to package any libraries needed in the ear, and automatically have any modules (EJB-JARs and WARs) use them -->
    <defaultLibBundleDir>lib</defaultLibBundleDir>
    <fileNameMapping>no-version</fileNameMapping>    
    <outputDirectory>C:\wildfly-8.1.0.Final\standalone\deployments</outputDirectory>
  </configuration>
</plugin>

In this section, we will build and deploy the application EAR module to the WildFly 8.x server. The pom.xml for the jboss-ejb3 Maven project specifies three modules: jboss-ejb3-ejb, jboss-ejb3-web, and jboss-ejb3-ear:

<modules>
  <module>jboss-ejb3-ejb</module>
  <module>jboss-ejb3-web</module>
  <module>jboss-ejb3-ear</module>
</modules>

Specify the JBoss AS version as 8.1.0.Final:

<version.jboss.as>8.1.0.Final</version.jboss.as>

The pom.xml for the jboss-ejb3 project specifies dependency on the jboss-ejb3-web and jboss-ejb3-ejb artifacts:

<dependency>
  <groupId>org.jboss.ejb3</groupId>
  <artifactId>jboss-ejb3-ejb</artifactId>
  <version>${project.version}</version>
  <type>ejb</type>
</dependency>
<dependency>
  <groupId>org.jboss.ejb3</groupId>
  <artifactId>jboss-ejb3-web</artifactId>
  <version>${project.version}</version>
  <type>war</type>
  <scope>compile</scope>
</dependency>

Next, we will build and deploy the EAR module to WildFly 8.x while the server is running. Right-click on pom.xml for the jboss-ejb3 Maven project and select Run As | Maven install, as shown in the following screenshot:

As the output from the pom.xml indicates all the three modules: ejb, web, and ear get built. The ear module gets copied to the deployments directory in WildFly 8.x:

Start the WildFly 8.x server if not already started. The jboss-ejb3.ear file gets deployed to the WildFly 8.x server and the jboss-ejb3-web context gets registered. The jboss-ejb3.ear.deployed file gets generated in the deployments directory, as shown in the following screenshot:

The EntityManager em persistence unit gets registered and the JNDI bindings for the CatalogSessionBeanFacade session bean gets generated:

Starting Persistence Unit (phase 1 of 2) Service 'jboss-ejb3-ear.ear/jboss-e
jb3-ejb.jar#em'
12:30:32,047 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Th
read Pool -- 50) HHH000204: Processing PersistenceUnitInfo [
  name: em
...]

The MySQL database tables for the entities get created, as shown in the following screenshot:

To log in to the WildFly 8 administration console, open http://localhost:8080 in any web browser. Click on the Administration Console link. Specify User Name and Password and click on Log In. Select the Runtime tab. The jboss-ejb3.ear application is listed as deployed in the Deployments | Manage Deployments section:

Next, open http://localhost:8080/jboss-ejb3-web/catalog.jsp and run the JSP client. The List of Catalogs gets displayed. The deleteSomeData method deletes Catalog for Oracle Magazine. As the Linux Magazine catalog does not have any data, the empty list gets displayed, as shown in the following screenshot:

The default JBoss Java EE EAR project created is a Java EE 6 project. If a Java EE 7 project is required to avail of the EJB 3.2, Servlet 3.1, JSF 2.2, and Hibernate JPA 2.1 APIs, the pom.xml for the ejb module and the web module subprojects should include the BOM (Bill of Materials) for Java EE 7 and the Nexus repository:

<repositories>
  <repository>
    <id>JBoss Repository</id>
    <url>https://repository.jboss.org/nexus/content/groups/public/</url>
  </repository>
</repositories>
<dependencyManagement>
  <dependencies>
      <dependency>
        <groupId>org.jboss.spec</groupId>
        <artifactId>jboss-javaee-7.0</artifactId>
        <version>1.0.0.Final</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
  </dependencies>
</dependencyManagement>

In addition the pom.xml for the ejb module and web module subprojects should specify the dependencies for the EJB 3.2, JSF 2.2, Servlet 3.1, and Hibernate JPA 2.1 specifications, as required, instead of the dependencies for the EJB 3.1, JSF 2.1, Servlet 3.0, and Hibernate JPA 2.0:

<dependency>
  <groupId>org.jboss.spec.javax.ejb</groupId>
  <artifactId>jboss-ejb-api_3.2_spec</artifactId>
  <scope>provided</scope>
</dependency>
<dependency>
  <groupId>org.hibernate.javax.persistence</groupId>
  <artifactId>hibernate-jpa-2.1-api</artifactId>
  <scope>provided</scope>
</dependency>
<dependency>
  <groupId>org.jboss.spec.javax.servlet</groupId>
  <artifactId>jboss-servlet-api_3.1_spec</artifactId>
  <scope>provided</scope>
</dependency>
<dependency>
  <groupId>org.jboss.spec.javax.faces</groupId>
  <artifactId>jboss-jsf-api_2.2_spec</artifactId>
  <scope>provided</scope>
</dependency>

In this chapter, we used the JBoss Tools plugin 4.2 in Eclipse Luna to generate a Java EE project for an EJB 3.x application in Eclipse IDE for Java EE Developers. We created entities to create a Catalog and used the Hibernate persistence provider to map the entities to the MySQL 5.6 database. Subsequently, we created a session bean façade for the entities. In the session bean, we created a catalog using the EntityManager API. We also created a JSP client to invoke the session bean facade using the local JNDI lookup and subsequently invoke the session bean methods to display database data. We used Maven to build the EJB, Web, and EAR modules and deploy the EAR module to WildFly 8.1. We ran the JSP client in a browser to fetch and display the data from the MySQL database. In the next chapter, we will discuss another database persistence technology: Hibernate.