Project's repository URL in README.md has been updated.

The project dependencies have been updated, including a change from
WildFly 8.2.1 to 10.1.0. This change affects the project configuration
in several ways, specially in tests configuration.

The README.md file has been updated to reflect the configuration
changes.

The database creation queries in the README.md file had a bug, as the ".*" to
reference all the tables in the databases was missing. This commit fixes this
bug and some minor indentation errors in this file.

The tests code for rest and service modules have been reviewed to
simplify and make it more readable. This change includes some
improvements on the OwnersDataset and some matchers classes.

The Bootstrap libraries (CSS and JavaScript libraries) were inserted in
the web pages (JSF module) through a CDN. Now, these libraries are added
as Maven dependencies, using the Webjars project packages.

In addition, the link and script tags used in the JSF template have been
replaced by the h:outputStylesheet and h:outputScript tags from JSF, as
this tags make consistent the use of relative paths though the different
pages of the application.

Finally, a minor error has been solved in the pets.xhtml file, as the
placeholder text for the birth field was assigned to the animal type
field.

The wildfly-mysql-run profile has been improved by changing the wildfly
goal added to the install phase to deploy-only instead of deploy. This
should reduce the startup time.

The JSF test execution has been disabled due to an error in the Gecko driver
that makes these test fail in some environments.

The default FirefoxDriver from Selenium no longer supports Firefox since
version 47 without a native web driver. This commit adds support to
native drivers, downloading and configuring this drivers depending on
the current OS (only Unix, Windows and Mac OS supported at this moment).

The JSF 2.2 specification recommends using CDI annotations (e.g. @Named,
@RequestScoped, etc.) instead of specific JSF annotations (e.g.
@ManagedBean, @RequestScoped, etc.). This commit replaces these
annotations following the recommendations. This change has some side
effects, as now the container does not automatically recognizes the
/faces route and JSF must be configured in the web.xml file. The new
configuration now processes every XHTML page as a JSF and the /faces
paths are no longer required or recognized.

The previous Maven configuration included a WildFly Maven plugin
configuration in the H2 and MySQL profiles that allowed the application
execution directly from Maven (with the mvn wildfly:start wildfly:deploy
command). As this configuration included a custom WildFly deployment
configuration (that modified the standalone.xml of the WildFly where the
application will be deployed), the mvn wildfly:deploy couldn't be used
to deploy the application in a local WildFly instance.

This commit adds a new profile (wildfly-mysql-run) that can be used to
execute the application directly from Maven (with the mvn install
command). The custom WildFly plugin configuration has been removed from
the other profiles, allowing users to normally deploy the application in
a running WildFly instances.

Instructions on how to use the profiles for application execution and
deployment can be found in the README.md file.

The project configuration has been simplified by unifying some part of
the mysql and h2 configurations.

In addition, the project has been configured to allow the execution of
the application with the Maven WildFly plugin.

The IsEqualToEntity matcher (previously, IsEqualsToEntity) has been
improved to allow property comparison by functional reference to the
getter methods of the properties to compare. Specifically, the
"checkAttribute" methods added allow providing a Function<T, R> as a
getter, where T is the type of the entity to compare and R is the type
returned by the getter method.

The datasource configuration now is done through the standalone.xml
instead of deploying the configuration.

Some test of the service and rest projects have been updated for better
coverage, achieving a 100% coverage in most of them.

On previous commits, the name of the EAR was changed but the Wildfly plugin
wasn't updated to use the new name. This commit changes the Wildfly deployment
configuration to fix this problem.

The JSF tests are misbehaving with the latest Firefox versions and,
therefore, they have been temporaly disabled.

The README.md has been update to reference the new course and the new
Eclipse version. In addition, the general pom.xml file has been updated
to include the newer versions of the dependencies, and the ear/pom.xml
has been modified to include more project information in the generated
EAR.

On the other hand, the testing mysql-ds.xml have been removed and the
standalone.xml testing files have been updated to include the datasource
data.

Missing version for compiler, javadoc, source and deploy plugin in POM was
causing some warning messages during the compilation with Maven.

In addition, the Javadoc was fixed in the OwnerService and PetService
classes.

SonarQube has a known problem with the 0.7.5 version of JaCoCo. This commit
solves this problem downgrading the JaCoCo version.

The JSF and REST modules are now served from the /xcs-sample path.

The source and javadoc of each proyect is deployed in the repository along with
the binaries.

The JaCoCo plugin has been added to perform the coverage test, while the
Wildfly plugins allows the automatic deployment of the project on a
Wildfly server using the 10990 port as the administration port.

This commit adds the instructions to run the application in a WildFly server.

This commit adds the JSF project with a web application that allows the
management of owners (by the administrators) and pets (by the owners).
The JSF project includes the functional tests for the owners management
page.

The EAR project only contains a POM that creates an EAR distribution of
the system.

The addition of the jboss-ejb3.xml file with the security domain
configuration allows the deployment of the "services" project as an
independent project in a Wildfly/JBoss container.

Some test classes have been refactorized for a more consistent use of
the OwnersDataset class and for a simpler test implementation.

An explanation of how Arquillian tests are configured and how to run the
Arquillian tests in the Eclipse project has been added to the root
README.md.

This matchers makes the Response status easier to check in tests.

The REST layer has been added but with incomplete tests. Students will
have to complete the tests.

This commit includes an important refactorization regarding tests. Test
classes and datasets have been moved from the "service" project to a new
"tests" project. This way, any project can include this "tests" project
as a dependency in order to have access to these common testing
resources.

This commit adds the OwnerService and PetService EJBs to the
implementation. This commit also includes the tests for this EJBs with
two different Wildfly profiles: a H2 profile and a MySQL profile.

The "administrator" entity has been added to represent the
administrators of the application.

This commit adds the test cases for the domain entities.

The first step is described and the sample points were reordered.

This commit includes the complete code for the domain entities.

Initial commit with a basic .gitignore, README.md and POM files.