The REST API now supports cross-origin requests thanks to a new CORS
configuration.

When the frontend tries to recover people list and the request fails a
message is shown to notify the user.

The user authentication was currently done using a cookie and following
the same style of token as the HTTP Basic authentication (i.e. a
concatenation of user and password joined with a ':' encoded with
base64).

This authentication has been replaced by a standard HTTP Basic
authentication.

Commit 9ef1c405 redesigned the user interface by introducing Bootstrap.
Although the structure changes where minimal, the changes on class types
caused the page object classes' selectors to fail.

This commit fixes this error and, in addition, fixes an unexpected error
on person deletion. This error was caused due to a missing wait for an
AJAX request response.

Some labels in the user interface were in Spanish and some in English.
This commit standardizes the language used to Spanish, translating every
label to that language.

Red background was added to the body of the login view for debugging
purposes, but shouldn't have passed to a stable release. This commit
removes the red background configuration.

The application appearance has been improved applying Bootstrap formats.

Some "console.logs" have been removed from the PeopleView class and the full
resposibility for the edition and deletion of people has been moved to public
methods of PeopleView.

The frontend has been refactorized to use classes in the JavaScript files.

A big refactorization has been done in this commit, focused on
simplifying the testing and execution process. The Spring-DbUnit library
has been added to allow the use of DbUnit through annotations in the
test classes. This change has been complemented with two new test
listeners that allow the creation of custom initial contexts and the use
of custom SQL scripts to create and destroy the database tables before
and after the test execution, respectively. In addition, all the tests
are executed now using a HSQLDB database.

The datasource configuration has been pulled out of the project, and now
it must be provided by the container.

The sample classes have been reviewed, refactorized and documented with
JavaDoc.

The POM file has been reworked to ease test and application execution
using maven. The new execution modes are:
	- The default execution includes unit, integration and acceptance (with
Selenium) test execution.
	- No acceptance tests: mvn -P -acceptance-tests-cargo <phase>
	- Run server for manual acceptance tests: mvn
-Dcargo.tomcat.start.skip=true -Dcargo.tomcat.run.skip=false
-DskipTests=true pre-integration-test 
	- Run server with MySQL database: mvn -P
run-tomcat-mysql,-acceptance-tests-cargo -DskipTests=true package
cargo:run

Web configuration for REST services and login filter was moved from the
web.xml file to code annotations.

POM was reviewed to update the dependencies of the project to the last
version and to improve the test execution.

Now it is possible to run the project with the testing database in a
Tomcat Server v7.0 using the mvn tomcat7:run goal. In addition, Selenium
tests now are executed as integration tests, starting the web server
before the test execution and stoping it after the tests end. Finally,
support for generating regular and cobertura test reports in HTML format
was also added.

The project was also cleaned by removing the MANIFEST.MF files and by
reallocating the SQL files.

DAO class modified to support and alternative JNDI for the data source
through the "db.jndi" system property. A new testing database resource
was added to the Context.xml file.

DAO tests use the "spring-test" library to create a JNDI context, as
JUnit doesn't create any context. Additionaly, a custom DataSource is
created using the "commons-dbcp" library and injected into the context.
Testing database creation scripts are provided in the mysql-tests.sql
file.

REST API is tested in the server side using the
"jersey-test-framework-provider-grizzly2" library. These tests also use
the "spring-test" and "commons-dbcp" libraries to create a context and
inject a custom data source.

REST API is tested in the client side using the "Selenium IDE" and
"RESTClient" plugins for Firefox. Manual database reset is required
before launching the test suite.

Web interface is tested using the "Selenium IDE" plugin for Firefox and
using the "Selenium WebDrive" in JUnit tests. Same tests are implemented
in both cases. Selenium IDE tests require a manual database reset before
launching the test suite. JUnit test require the server to be started
using the testing database.

Access to any resource except index.html can be restricted enabling the
LoginFilter in the web.xml configuration file. It is currently disabled.

Old index.html moved to main.html and replaced with an index.html that
contains a login form.

RESTful API modified to use PUT, DELETE, POST and GET methods.

In this first version, this applicacion includes a complete CRUD using
an AJAX+JSON+REST architecture.