java-ee-kickoff-app ![Build Status](https://camo.githubusercontent.com/6cba851048cb08325486aa990d2c2c74ae16db9cd7dbefd97eca5549f9c88c4b/68747470733a2f2f7472617669732d63692e6f72672f6a61766165656b69636b6f66662f6a6176612d65652d6b69636b6f66662d6170702e7376673f6272616e63683d6d6173746572)
Basic project template to kickoff a new Java EE web application. Live demo is temporarily down. It's expected to return mid June 2018.
Usage
Clone the branch matching your target environment into a new project. There are currently three branches available.
Note: For usage on JBoss EAP 7 alpha/beta or WildFly 10rc4 and below, JASPIC needs to be activated before the application can be deployed. See also http://arjan-tijms.omnifaces.org/2015/08/activating-jaspic-in-jboss-wildfly.html
Database
The default app uses H2 with drop-and-create
. In other words, the default app uses an embedded database and is configured to drop and create all tables on startup. If you want to stop dropping all tables on startup, edit javax.persistence.schema-generation.database.action
property of /META-INF/persistence.xml
to create
. If you want to change the database, install the desired JDBC driver in your target server and edit the JDBC driver configuration in /META-INF/conf/datasource-settings.xml
. It's not necessary to manually create a data source in the target server as that's already done via <data-source>
in web.xml
.