<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">

<?asciidoc-toc?>

<?asciidoc-numbered?>

<book xmlns="http://docbook.org/ns/docbook" lang="en">

<bookinfo>

<title>Java EE 7 Hands-on Lab</title>

<date>Jun 25, 2014</date>

<author>

<firstname>Arun</firstname>

<surname>Gupta</surname>

<email>https://twitter.com/arungupta[@arungupta]</email>

</author>

<authorinitials>AG</authorinitials>

<revhistory>

<revision>

<revnumber>2.1</revnumber>

<date>Jun 25, 2014</date>

<authorinitials>AG</authorinitials>

</revision>

</revhistory>

</bookinfo>

<chapter id="_introduction">

<title>Introduction</title>

<simpara>The Java EE 7 platform continues the ease of development push that

characterized prior releases by bringing further simplification to

enterprise development. It adds new and important APIs such as the REST

client API in JAX-RS 2.0 and the long awaited Batch Processing API. Java

Message Service 2.0 has undergone an extreme makeover to align with the

improvements in the Java language. There are plenty of improvements to

several other components. Newer web standards like HTML 5, WebSocket,

and JSON processing are embraced to build modern web applications.</simpara>

<simpara>This hands-on lab will build a typical 3-tier end-to-end application

using the following Java EE 7 technologies:</simpara>

<itemizedlist>

<listitem>

<simpara>Java API for WebSocket 1.0 (JSR 356)</simpara>

</listitem>

<listitem>

<simpara>Batch Applications for the Java Platform 1.0 (JSR 352)</simpara>

</listitem>

<listitem>

<simpara>Java API for JSON Processing 1.0 (JSR 353)</simpara>

</listitem>

<listitem>

<simpara>Java API for RESTful Web Services 2.0 (JSR 339)</simpara>

</listitem>

<listitem>

<simpara>Java Message Service 2.0 (JSR 343)</simpara>

</listitem>

<listitem>

<simpara>Java Persistence API 2.1 (JSR 338)</simpara>

</listitem>

<listitem>

<simpara>JavaServer Faces 2.2 (JSR 344)</simpara>

</listitem>

<listitem>

<simpara>Contexts and Dependency Injection 1.1 (JSR 346)</simpara>

</listitem>

<listitem>

<simpara>Bean Validation 1.1 (JSR 349)</simpara>

</listitem>

<listitem>

<simpara>Java Transaction API 1.2 (JSR 907)</simpara>

</listitem>

</itemizedlist>

<simpara>Together these APIs will allow you to be more productive by simplifying enterprise development.</simpara>

<simpara>The latest version of this document can be downloaded from <ulink url="https://github.com/javaee-samples/javaee7-hol/blob/master/docs/asciidoc/javaee7-hol.html">javaee7-hol.html</ulink>. Please file issues or send pull requests for any updates.</simpara>

<section id="_software_requirement">

<title>Software Requirement</title>

<simpara>The following software needs to be downloaded and installed:</simpara>

<itemizedlist>

<listitem>

<simpara>JDK 7 from

<ulink url="http://www.oracle.com/technetwork/java/javase/downloads/index.html">http://www.oracle.com/technetwork/java/javase/downloads/index.html</ulink>.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">Application Server</emphasis>: This lab can use WildFly 8 or GlassFish 4 as the application server. This document provides instructions for

WildFly 8.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">IDE</emphasis>: NetBeans 8.0+, JBoss Developer Studio (Eclipse-based), or IntelliJ IDEA 13 can be used. This document provides instructions for

NetBeans 8.</simpara>

<simpara>Download &#8220;All&#8221; or &#8220;Java EE&#8221; version from

<ulink url="http://netbeans.org/downloads/">http://netbeans.org/downloads/</ulink>. A

snapshot of the downloads page is shown and highlights the exact

&#8216;Download&#8217; button to be clicked.</simpara>

<figure>

<title>NetBeans download</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/1.1-netbeans-download.png"/>

</imageobject>

<textobject><phrase>1.1 netbeans download</phrase></textobject>

</mediaobject>

</figure>

<simpara>WildFly 8 needs to be downloaded from <ulink url="http://wildfly.org/downloads/">wildfly.org</ulink> and configured in NetBeans IDE following the instructions in <xref linkend="appendix-wildfly-netbeans"/>.</simpara>

<tip>

<simpara><xref linkend="appendix-wildfly-idea"/> explains how to configure WildFly in IntelliJ IDEA.</simpara>

</tip>

</listitem>

</itemizedlist>

</section>

</chapter>

<chapter id="_problem_statement">

<title>Problem Statement</title>

<simpara>This hands-on lab builds a typical 3-tier Java EE 7 Web application that

allows customers to view the show timings for a movie in a 7-theater

Cineplex and make reservations. Users can add new movies and delete

existing movies. Customers can discuss the movie in a chat room. Total

sales from each showing are calculated at the end of the day. Customers

also accrue points for watching movies.</simpara>

<figure>

<title>Architecture diagram</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/2.0-problem-statement.png"/>

</imageobject>

<textobject><phrase>2.0 problem statement</phrase></textobject>

</mediaobject>

</figure>

<simpara>This figure shows the key components of the application. The User

Interface initiates all the flows in the application. Show Booking,

Add/Delete Movie and Ticket Sales interact with the database; Movie

Points may interact with the database, however, this is out of scope for

this application; and Chat Room does not interact with the database.</simpara>

<simpara>The different functions of the application, as detailed above, utilize

various Java technologies and web standards in their implementation. The

following figure shows how Java EE technologies are used in different

flows.</simpara>

<figure>

<title>Technologies used in the application</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/2.0-technologies.png"/>

</imageobject>

<textobject><phrase>2.0 technologies</phrase></textobject>

</mediaobject>

</figure>

<simpara>The table below details the components and the selected technology used

in its’ implementation.</simpara>

<informaltable frame="all"

rowsep="1" colsep="1">

<tgroup cols="2">

<colspec colname="col_1" colwidth="20*"/>

<colspec colname="col_2" colwidth="80*"/>

<thead>

<row>

<entry align="left" valign="top">Flow</entry>

<entry align="left" valign="top">Description</entry>

</row>

</thead>

<tbody>

<row>

<entry align="left" valign="top"><simpara>User Interface</simpara></entry>

<entry align="left" valign="top"><simpara>Written entirely in <emphasis>JavaServer Faces</emphasis> (JSF)</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara>Chat Room</simpara></entry>

<entry align="left" valign="top"><simpara>Utilizes client-side JavaScript and JSON to communicate with a <emphasis>WebSocket</emphasis> endpoint</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara>Ticket Sales</simpara></entry>

<entry align="left" valign="top"><simpara>Uses <emphasis>Batch Applications for the Java Platform</emphasis> to calculate the total

sales and persist to the database.</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara>Add/Delete Movie</simpara></entry>

<entry align="left" valign="top"><simpara>Implemented using RESTful Web Services. JSON is used as on-the-wire data format</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara>Movie Points</simpara></entry>

<entry align="left" valign="top"><simpara>Uses <emphasis>Java Message Service</emphasis> (JMS) to update and obtain loyalty reward

points; an optional implementation using database technology may be

performed</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara>Show Booking</simpara></entry>

<entry align="left" valign="top"><simpara>Uses lightweight <emphasis>Enterprise JavaBeans</emphasis> to communicate with the database

using Java Persistence API</simpara></entry>

</row>

</tbody>

</tgroup>

</informaltable>

<simpara>This document is not a comprehensive tutorial of Java EE. The attendees

are expected to know the basic Java EE concepts such as EJB, JPA,

JAX-RS, and CDI. The <ulink url="http://docs.oracle.com/javaee/7/tutorial/doc/">Java

EE 7 Tutorial</ulink> is a good place to learn all these concepts. However

enough explanation is provided in this guide to get you started with the

application.</simpara>

<warning>

<simpara>This is a sample application and the code may not be

following the best practices to prevent SQL injection, cross-side

scripting attacks, escaping parameters, and other similar features

expected of a robust enterprise application. This is intentional such as

to stay focused on explaining the technology. It is highly recommended

to make sure that the code copied from this sample application is

updated to meet those requirements.</simpara>

</warning>

<section id="_lab_flow">

<title>Lab Flow</title>

<simpara>The attendees will start with an existing maven application and by

following the instructions and guidance provided by this lab they will:</simpara>

<itemizedlist>

<listitem>

<simpara>Read existing source code to gain an understanding of the structure of

the application and use of the selected platform technologies.</simpara>

</listitem>

<listitem>

<simpara>Add new and update existing code with provided fragments in order to

demonstrate usage of different technology stacks in the Java EE 7

platform.</simpara>

</listitem>

</itemizedlist>

<simpara>While you are copy/pasting the code from this document into NetBeans,

here are couple of tips that will be really useful and make your

experience enjoyable!</simpara>

<variablelist>

<varlistentry>

<term>Source Code Formatting</term>

<listitem>

<simpara>NetBeans provides capability to neatly format the source code

following conventions. This can be done for any type of source code,

whether its XML or Java or something else. It is highly recommended to

use this functionality after the code is copy/pasted from this document

to the editor. This keeps the code legible.</simpara>

<simpara>This functionality can be accessed by right-clicking in the editor pane

and selecting “Format” as shown.</simpara>

<figure>

<title>Format code in NetBeans</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/2.1-format.png"/>

</imageobject>

<textobject><phrase>2.1 format</phrase></textobject>

</mediaobject>

</figure>

<simpara>This functionality is also accessible using the following keyboard

shortcuts:</simpara>

<informaltable frame="all"

rowsep="1" colsep="1">

<?dbhtml table-width="50%"?>

<?dbfo table-width="50%"?>

<?dblatex table-width="50%"?>

<tgroup cols="2">

<colspec colname="col_1" colwidth="107*"/>

<colspec colname="col_2" colwidth="107*"/>

<thead>

<row>

<entry align="left" valign="top">Shortcut</entry>

<entry align="left" valign="top">Operating System</entry>

</row>

</thead>

<tbody>

<row>

<entry align="left" valign="top"><simpara><keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>F</keycap></keycombo></simpara></entry>

<entry align="left" valign="top"><simpara>OSX</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><keycombo><keycap>Alt</keycap><keycap>Shift</keycap><keycap>F</keycap></keycombo></simpara></entry>

<entry align="left" valign="top"><simpara>Windows</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><keycombo><keycap>Alt</keycap><keycap>Shift</keycap><keycap>F</keycap></keycombo></simpara></entry>

<entry align="left" valign="top"><simpara>Linux</simpara></entry>

</row>

</tbody>

</tgroup>

</informaltable>

</listitem>

</varlistentry>

<varlistentry>

<term>Automatic Imports</term>

<listitem>

<simpara>Copy/pasting the Java code from this document in NetBeans editor does

not auto-import the classes. This is required to be done manually in

order for the classes to compile. This can be fixed for each missing

import statement by clicking on the yellow bulb shown in the side bar.</simpara>

<figure>

<title>ServerEndpoint import</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/2.1-server-endpoint.png"/>

</imageobject>

<textobject><phrase>2.1 server endpoint</phrase></textobject>

</mediaobject>

</figure>

<simpara>Alternatively all the imports can be resolved by right-clicking on the

editor pane and selecting &#8220;Fix Imports&#8221; as shown.</simpara>

<figure>

<title>Fix Imports in NetBeans</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/2.1-fix-imports.png"/>

</imageobject>

<textobject><phrase>2.1 fix imports</phrase></textobject>

</mediaobject>

</figure>

<simpara>This functionality is also accessible using the following keyboard

shortcuts:</simpara>

<informaltable frame="all"

rowsep="1" colsep="1">

<?dbhtml table-width="50%"?>

<?dbfo table-width="50%"?>

<?dblatex table-width="50%"?>

<tgroup cols="2">

<colspec colname="col_1" colwidth="107*"/>

<colspec colname="col_2" colwidth="107*"/>

<thead>

<row>

<entry align="left" valign="top">Shortcut</entry>

<entry align="left" valign="top">Operating System</entry>

</row>

</thead>

<tbody>

<row>

<entry align="left" valign="top"><simpara><keycombo><keycap>Command</keycap><keycap>Shift</keycap><keycap>I</keycap></keycombo></simpara></entry>

<entry align="left" valign="top"><simpara>OSX</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>I</keycap></keycombo></simpara></entry>

<entry align="left" valign="top"><simpara>Windows</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>I</keycap></keycombo></simpara></entry>

<entry align="left" valign="top"><simpara>Linux</simpara></entry>

</row>

</tbody>

</tgroup>

</informaltable>

<simpara>The defaults may work in most of the cases. Choices are shown in case a

class is available to import from multiple packages. If multiple

packages are available then specific packages to import from are clearly

marked in the document.</simpara>

</listitem>

</varlistentry>

</variablelist>

</section>

<section id="_estimated_time">

<title>Estimated Time</title>

<simpara>Following the complete instructions in this document can take any where

from two to four hours. The wide time range accommodates for learning

the new technologies, finding your way in NetBeans, copy/pasting the

code, and debugging the errors.</simpara>

<simpara>The recommended flow is where you follow through the instructions in all

sections in the listed sequence. Alternatively, you may like to cover

section <xref linkend="walk-through"/> through <xref linkend="jsf"/> in an order of your choice, based upon your

interest and preference of the technology. However section <xref linkend="jaxrs"/> is a

pre-requisite for <xref linkend="json"/>.</simpara>

<simpara>Here is an approximate time estimate for each section:</simpara>

<informaltable frame="all"

rowsep="1" colsep="1">

<tgroup cols="2">

<colspec colname="col_1" colwidth="66*"/>

<colspec colname="col_2" colwidth="33*"/>

<thead>

<row>

<entry align="left" valign="top">Section Title</entry>

<entry align="left" valign="top">Estimated Time</entry>

</row>

</thead>

<tbody>

<row>

<entry align="left" valign="top"><simpara><xref linkend="walk-through"/></simpara></entry>

<entry align="left" valign="top"><simpara>15 - 30 mins</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><xref linkend="websocket"/></simpara></entry>

<entry align="left" valign="top"><simpara>30 - 45 mins</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><xref linkend="batch"/></simpara></entry>

<entry align="left" valign="top"><simpara>30 - 45 mins</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><xref linkend="jaxrs"/></simpara></entry>

<entry align="left" valign="top"><simpara>30 - 45 mins</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><xref linkend="json"/></simpara></entry>

<entry align="left" valign="top"><simpara>30 - 45 mins</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><xref linkend="jms"/></simpara></entry>

<entry align="left" valign="top"><simpara>30 - 45 mins</simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><xref linkend="jsf"/></simpara></entry>

<entry align="left" valign="top"><simpara>30 - 45 mins</simpara></entry>

</row>

</tbody>

</tgroup>

</informaltable>

<simpara>The listed time for each section is only an estimate and by no means

restrict you within that. These sections have been completed in much

shorter time, and you can do it too!</simpara>

<tip>

<simpara>The listed time for each section also allows you to create a custom

version of the lab depending upon your target audience and available

time.</simpara>

</tip>

</section>

</chapter>

<chapter id="walk-through">

<title>Walk-through of Sample Application</title>

<simpara><emphasis role="strong">Purpose</emphasis>: This section will download the sample application to be used

in this hands-on lab. A walk-through of the application will be

performed to provide an understanding of the application architecture.</simpara>

<simpara><emphasis role="strong">Estimated Time</emphasis>: 15-30 mins</simpara>

<orderedlist numeration="arabic">

<listitem>

<simpara>Download the sample application from

<ulink url="https://github.com/javaee-samples/javaee7-hol/blob/master/starting-template/movieplex7-starting-template.zip?raw=true">movieplex7-starting-template.zip</ulink>

and unzip. This will create a &#8216;movieplex7&#8217; directory and unzips all the

content there.</simpara>

</listitem>

<listitem>

<simpara>In NetBeans IDE, select &#8216;File&#8217;, &#8216;Open Project&#8217;, select the

unzipped directory, and click on &#8216;Open Project&#8217;. The project structure

is shown.</simpara>

<figure>

<title>Project structure in NetBeans</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/3.2-project-structure.png"/>

</imageobject>

<textobject><phrase>3.2 project structure</phrase></textobject>

</mediaobject>

</figure>

</listitem>

<listitem>

<simpara>Maven Coordinates: Expand &#8216;Project Files&#8217; and double click on

&#8216;pom.xml&#8217;. In the &#8216;pom.xml&#8217;, the Java EE 7 API is specified as a

&lt;dependency&gt;:</simpara>

<programlisting language="xml" linenumbering="unnumbered">&lt;dependencies&gt;

&lt;dependency&gt;

&lt;groupId&gt;javax&lt;/groupId&gt;

&lt;artifactId&gt;javaee-api&lt;/artifactId&gt;

&lt;version&gt;7.0&lt;/version&gt;

&lt;scope&gt;provided&lt;/scope&gt;

&lt;/dependency&gt;

&lt;/dependencies&gt;</programlisting>

<simpara>This will ensure that Java EE 7 APIs are retrieved from the central

Maven repository.</simpara>

<note>

<simpara>The Java EE 6 platform introduced the notion of &#8216;profiles&#8217;. A profile is

a configuration of the Java EE platform targeted at a specific class of

applications. All Java EE profiles share a set of common features, such

as naming and resource injection, packaging rules, security

requirements, etc. A profile may contain a proper subset or superset of

the technologies contained in the platform.</simpara>

<simpara>The Java EE Web Profile is a profile of the Java EE Platform

specifically targeted at modern web applications. The complete set of

specifications defined in the Web Profile is defined in the Java EE 7

Web Profile Specification.</simpara>

</note>

<simpara>WildFly can be started in Full Platform or Web Profile.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">Default Data Source</emphasis>: Expand &#8216;Other Sources&#8217;,

&#8216;src/main/resources&#8217;, &#8216;META-INF&#8217;, and double-click on &#8216;persistence.xml&#8217;.

By default, NetBeans opens the file in Design View. Click on &#8216;Source&#8217; tab

to view the XML source.</simpara>

<figure>

<title>persistence.xml</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/3.2-persistence-xml.png"/>

</imageobject>

<textobject><phrase>3.2 persistence xml</phrase></textobject>

</mediaobject>

</figure>

<simpara>It looks like:</simpara>

<programlisting language="xml" linenumbering="unnumbered">&lt;?xml version="1.0" encoding="UTF-8"?&gt;

&lt;persistence

version="2.1"

xmlns="http://xmlns.jcp.org/xml/ns/persistence"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence

http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"&gt;

&lt;persistence-unit name="movieplex7PU" transaction-type="JTA"&gt;

&lt;!--

&lt;jta-data-source&gt;java:comp/DefaultDataSource&lt;/jta-data-source&gt;

--&gt;

&lt;properties&gt;

&lt;property

name="javax.persistence.schema-generation.database.action"

value="drop-and-create"/&gt;

&lt;property

name="javax.persistence.schema-generation.create-source"

value="script"/&gt;

&lt;property

name="javax.persistence.schema-generation.drop-source"

value="script"/&gt;

&lt;property

name="javax.persistence.schema-generation.drop-script-source"

value="META-INF/drop.sql"/&gt;

&lt;property

name="javax.persistence.sql-load-script-source"

value="META-INF/load.sql"/&gt;

&lt;property

name="eclipselink.deploy-on-startup"

value="true"/&gt;

&lt;property

name="eclipselink.logging.exceptions"

value="false"/&gt;

&lt;/properties&gt;

&lt;/persistence-unit&gt;

&lt;/persistence&gt;</programlisting>

<simpara>Notice <literal>&lt;jta-data-source&gt;</literal> is commented out, i.e. no data source element

is specified. This element identifies the JDBC resource to connect to in

the runtime environment of the underlying application server.</simpara>

<simpara>The Java EE 7 platform defines a new default data source that must be

provided by the runtime. This pre-configured data source is accessible

under the JNDI name</simpara>

<programlisting language="java" linenumbering="unnumbered">java:comp/DefaultDataSource</programlisting>

<simpara>The JPA 2.1 specification says if neither <literal>jta-data-source</literal> nor

<literal>non-jta-data-source</literal> elements are specified, the deployer must specify a

JTA data source or the default JTA data source must be provided by the

container.</simpara>

<simpara>For WildFly 8, the default data source is bound to the JDBC resource <literal>what name</literal>.</simpara>

<simpara>Clicking back and forth between &#8216;Design&#8217; and &#8216;Source&#8217; view may prompt

the error shown below:</simpara>

<figure>

<title>Missing server error from persistence.xml</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/3.4-missing-server.png"/>

</imageobject>

<textobject><phrase>3.4 missing server</phrase></textobject>

</mediaobject>

</figure>

<simpara>This will get resolved when we run the application. Click on &#8216;OK&#8217; to

dismiss the dialog.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">Schema Generation:</emphasis> JPA 2.1 defines a new set of

<literal>javax.persistence.schema-generation.*</literal> properties that can be used to

generate database artifacts like tables, indexes, and constraints in a

database schema. This helps in prototyping of your application where the

required artifacts are generated either prior to application deployment

or as part of <literal>EntityManagerFactory</literal> creation. This feature will allow

your JPA domain object model to be directly generated in a database. The

generated schema may need to be tuned for actual production environment.</simpara>

<simpara>The &#8220;persistence.xml&#8221; in the application has the following

<literal>javax.persistence.schema-generation.*</literal> properties. Their meaning and

possible values are explained:</simpara>

<informaltable frame="all"

rowsep="1" colsep="1">

<tgroup cols="3">

<colspec colname="col_1" colwidth="33*"/>

<colspec colname="col_2" colwidth="33*"/>

<colspec colname="col_3" colwidth="33*"/>

<thead>

<row>

<entry align="left" valign="top">Property</entry>

<entry align="left" valign="top">Meaning</entry>

<entry align="left" valign="top">Values</entry>

</row>

</thead>

<tbody>

<row>

<entry align="left" valign="top"><simpara><literal>javax.persistence.schema-generation.database.action</literal></simpara></entry>

<entry align="left" valign="top"><simpara>Specifies the action to be taken by the persistence provider with regard

to the database artifacts.</simpara></entry>

<entry align="left" valign="top"><simpara><literal>none</literal>, <literal>create</literal>, <literal>drop-and-create</literal>, <literal>drop</literal></simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>javax.persistence.schema-generation.create-source</literal>

<literal>javax.persistence.schema-generation.drop-source</literal></simpara></entry>

<entry align="left" valign="top"><simpara>Specifies whether the creation or deletion of database artifacts is to

occur on the basis of the object/relational mapping metadata, DDL

script, or a combination of the two.</simpara></entry>

<entry align="left" valign="top"><simpara><literal>metadata</literal>, <literal>script</literal>, <literal>metadata-then-script</literal>, <literal>script-then-metadata</literal></simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>javax.persistence.schema-generation.create-script-source</literal>

<literal>javax.persistence.schema-generation.drop-script-source</literal></simpara></entry>

<entry align="left" valign="top"><simpara>Specifies a <literal>java.IO.Reader</literal> configured for reading of the SQL script or a

string designating a file URL for the SQL script to create or delete

database artifacts.</simpara></entry>

<entry align="left" valign="top"></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>javax.persistence.sql-load-script-source</literal></simpara></entry>

<entry align="left" valign="top"><simpara>Specifies a <literal>java.IO.Reader</literal> configured for reading of the SQL load script

for database initialization or a string designating a file URL for the

script.</simpara></entry>

<entry align="left" valign="top"></entry>

</row>

</tbody>

</tgroup>

</informaltable>

<simpara>Refer to the <ulink url="http://jcp.org/en/jsr/detail?id=338">JPA 2.1 Specification</ulink>

for a complete understanding of these properties.</simpara>

<simpara>In the application, the scripts are bundled in the WAR file in

&#8216;META-INF&#8217; directory. As the location of these scripts is specified as a

URL, the scripts may be loaded from outside the WAR file as well.</simpara>

<simpara>Feel free to open &#8216;create.sql&#8217;, &#8216;drop.sql&#8217; and &#8216;load.sql&#8217; and read

through the SQL scripts. The database schema is shown.</simpara>

<figure>

<title>Database schema</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/3.5-schema.png"/>

</imageobject>

<textobject><phrase>3.5 schema</phrase></textobject>

</mediaobject>

</figure>

<simpara>This folder also contains &#8216;sales.csv&#8217; which carries some comma-separated

data, and is used later in the application.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">JPA entities, Stateless EJBs, and REST endpoints</emphasis>: Expand <literal>Source

Packages'. The package `org.javaee7.movieplex7.entities</literal> contains the

JPA entities corresponding to the database table definitions. Each JPA

entity has several convenient <literal>@NamedQuery</literal> defined and uses Bean

Validation constraints to enforce validation.</simpara>

<simpara>The package <literal>org.javaee7.movieplex7.rest</literal> contains stateless EJBs

corresponding to different JPA entities.</simpara>

<simpara>Each EJB has methods to perform CRUD operations on the JPA entity and

convenience query methods. Each EJB is also EL-injectable (@Named) and

published as a REST endpoint (@Path). The AplicationConfig class defines

the base path of REST endpoint. The path for the REST endpoint is the

same as the JPA entity class name.</simpara>

<simpara>The mapping between JPA entity classes, EJB classes, and the URI of the

corresponding REST endpoint is shown.</simpara>

<informaltable frame="all"

rowsep="1" colsep="1">

<tgroup cols="3">

<colspec colname="col_1" colwidth="33*"/>

<colspec colname="col_2" colwidth="33*"/>

<colspec colname="col_3" colwidth="33*"/>

<thead>

<row>

<entry align="left" valign="top">JPA Entity Class</entry>

<entry align="left" valign="top">EJB Class</entry>

<entry align="left" valign="top">RESTful Path</entry>

</row>

</thead>

<tbody>

<row>

<entry align="left" valign="top"><simpara><literal>Movie</literal></simpara></entry>

<entry align="left" valign="top"><simpara><literal>MovieFacadeREST</literal></simpara></entry>

<entry align="left" valign="top"><simpara><emphasis>/webresources/movie</emphasis></simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>Sales</literal></simpara></entry>

<entry align="left" valign="top"><simpara><literal>SalesFacadeREST</literal></simpara></entry>

<entry align="left" valign="top"><simpara><emphasis>/webresources/sales</emphasis></simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>ShowTiming</literal></simpara></entry>

<entry align="left" valign="top"><simpara><literal>ShowTimingFacadeREST</literal></simpara></entry>

<entry align="left" valign="top"><simpara><emphasis>/webresources/showtiming</emphasis></simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>Theater</literal></simpara></entry>

<entry align="left" valign="top"><simpara><literal>TheaterFacadeREST</literal></simpara></entry>

<entry align="left" valign="top"><simpara><emphasis>/webresources/theater</emphasis></simpara></entry>

</row>

<row>

<entry align="left" valign="top"><simpara><literal>Timeslot</literal></simpara></entry>

<entry align="left" valign="top"><simpara><literal>TimeslotFacadeREST</literal></simpara></entry>

<entry align="left" valign="top"><simpara><emphasis>/webresources/timeslot</emphasis></simpara></entry>

</row>

</tbody>

</tgroup>

</informaltable>

<simpara>Feel free to browse through the code.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">JSF pages</emphasis>: &#8216;WEB-INF/template.xhtml&#8217; defines the template of the

web page and has a header, left navigation bar, and a main content

section. &#8216;index.xhtml&#8217; uses this template and the EJBs to display the

number of movies and theaters.</simpara>

<simpara>Java EE 7 enables CDI discovery of beans by default. No &#8216;beans.xml&#8217; is

required in &#8216;WEB-INF&#8217;. This allows all beans with bean defining

annotation, i.e. either a bean with an explicit CDI scope or EJBs to be

available for injection.</simpara>

<simpara>Note, &#8216;template.xhtml&#8217; is in &#8216;WEB-INF&#8217; folder as it allows the template

to be accessible from the pages bundled with the application only. If it

were bundled with rest of the pages then it would be accessible outside

the application and thus allowing other external pages to use it as

well.</simpara>

</listitem>

<listitem>

<simpara><emphasis role="strong">Run the sample</emphasis>: Right-click on the project and select &#8216;Run&#8217;.

This will download all the maven dependencies on your machine, build a

WAR file, deploy on

WildFly 8

, and show the URL

<ulink url="http://localhost:8080/movieplex7">localhost:8080/movieplex7</ulink> in the

default browser configured in NetBeans. Note that this could take a

while if you have never built a Maven application on your machine.</simpara>

<tip>

<simpara>The project will show red squiggly lines in the source code indicating

that the classes cannot be resolved. This is expected before the

dependencies are downloaded. However these references will be resolved

correctly after the dependencies are downloaded during project building.</simpara>

</tip>

<simpara>During the first run, the IDE will ask you to select a deployment server.

Choose the configured WildFly server and click on &#8216;OK&#8217;.</simpara>

<figure>

<title>WildFly deployment server</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/3.6-wildfly-server.png"/>

</imageobject>

<textobject><phrase>3.6 wildfly server</phrase></textobject>

</mediaobject>

</figure>

<simpara>The output looks like as shown.</simpara>

<figure>

<title>Application main page</title>

<mediaobject>

<imageobject>

<imagedata fileref="images/3.8-first-page.png"/>

</imageobject>

<textobject><phrase>3.8 first page</phrase></textobject>

</mediaobject>

</figure>

</listitem>

</orderedlist>

</chapter>

<chapter id="websocket">

<title>Chat Room (Java API for WebSocket)</title>

<simpara><emphasis role="strong">Purpose</emphasis>: Build a chat room for viewers. In doing so several new

features of Java API for WebSocket 1.0 will be introduced and

demonstrated by using them in the application.</simpara>

<simpara><emphasis role="strong">Estimated Time</emphasis>: 30-45 mins</simpara>

<simpara>WebSocket provide a full-duplex and bi-directional communication

protocol over a single TCP connection. WebSocket is a combination of

<ulink url="http://tools.ietf.org/html/rfc6455">IETF RFC 6455</ulink>

<ulink url="http://tools.ietf.org/html/rfc6455">Protocol</ulink> and

<ulink url="http://www.w3.org/TR/websockets/">W3C JavaScript WebSocket API</ulink> (a

Candidate Recommendation as of this writing). The protocol defines an

opening handshake and data transfer. The API enables Web pages to use

the WebSocket protocol for two-way communication with the remote host.</simpara>

<simpara><ulink url="http://jcp.org/en/jsr/detail?id=356">JSR 356</ulink> defines a standard API for

creating WebSocket applications in the Java EE 7 Platform. The JSR

provides support for:</simpara>

<itemizedlist>

<listitem>

<simpara>Create WebSocket endpoint using annotations and interface</simpara>

</listitem>

<listitem>

<simpara>Initiating and intercepting WebSocket events</simpara>

</listitem>

<listitem>

<simpara>Creation and consumption of WebSocket text and binary messages</simpara>

</listitem>

<listitem>

<simpara>Configuration and management of WebSocket sessions</simpara>

</listitem>

<listitem>

<simpara>Integration with Java EE security model</simpara>

</listitem>