Enterprise Java Development@TOPIC@
The project created from this archetype has two mechanisms for managing schema; maven plugin-based and entitymanager-based. Know that when you start this exercise the two mechanisms may be both activated and competing (last one wins). One type may be better for some usages while the other may be more helpful in others. Know which is best to use in which circumstance and which one is active or turned off when encountering a database setup issue.
The entitymanager mechanism is activated and deactivated through the hibernate.hbm2ddl.auto property in src/test/resources/hibernate.properties. Set to create to turn on or comment out to turn off.
# src/test/resources/hibernate.properties ... #hibernate.hbm2ddl.auto=create
The maven plugin mechanism is turned activated by the sql-maven-plugin within the local pom.xml. You can either comment out the entire plugin, or comment out or mangle key sections of the plugin definition in order to turn off this capability.
# pom.xml
<!-- runs schema against the DB
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>sql-maven-plugin</artifactId>
...
</plugin>
-->
The entitymanager technique is useful when making quick schema changes to your entities within Eclipse but not as good if you want to preserve data for analysis. The maven plugin technique is useful when you commonly build from maven after making entity changes. It is also useful in generating schema that can be analyzed after the build is complete.
Add the following to your .m2/settings.xml file. This will allow you to resolve the exercise archetype and set a default database for the exercise.
<profiles>
<profile>
<id>webdev-repositories</id>
<repositories>
<repository>
<id>webdev-baseline</id>
<name>webdev.apl.jhu.edu baseline</name>
<url>http://webdev.apl.jhu.edu/~jcs/maven2</url>
</repository>
<repository>
<id>webdev-snapshot</id>
<name>webdev.apl.jhu.edu SNAPSHOT</name>
<url>http://webdev.apl.jhu.edu/~jcs/maven2-snapshot</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>webdev-plugins</id>
<name>ejava webdev repository</name>
<url>http://webdev.apl.jhu.edu/~jcs/maven2</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>h2db</activeProfile>
<!--
<activeProfile>h2srv</activeProfile>
-->
</activeProfiles>
Use the ejava.jpa:jpa-archetype to setup a new Maven project for this exercise. Activate the webdev-repositories profile (-Pwebdev-repositories) so that you can resolve the archetype off the Internet.
$ mvn archetype:generate -B \ -DarchetypeGroupId=ejava.jpa -DarchetypeArtifactId=jpa-archetype \ -DgroupId=myorg.entityex -DartifactId=entityEx \ -Pwebdev-repositories [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building JPA Entity 3.0.2013.1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-archetype-plugin:2.2:generate (default-cli) @ jpa-entity >>> [INFO] [INFO] <<< maven-archetype-plugin:2.2:generate (default-cli) @ jpa-entity <<< [INFO] [INFO] --- maven-archetype-plugin:2.2:generate (default-cli) @ jpa-entity --- [INFO] Generating project in Batch mode [INFO] Archetype [ejava.jpa:jpa-archetype:3.0.2013.1-SNAPSHOT] found in catalog local [INFO] ---------------------------------------------------------------------------- [INFO] Using following parameters for creating project from Archetype: jpa-archetype:3.0.2013.1-SNAPSHOT [INFO] ---------------------------------------------------------------------------- [INFO] Parameter: groupId, Value: myorg.entityex [INFO] Parameter: artifactId, Value: entityEx [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: package, Value: myorg.entityex [INFO] Parameter: packageInPathFormat, Value: myorg/entityex [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: package, Value: myorg.entityex [INFO] Parameter: groupId, Value: myorg.entityex [INFO] Parameter: artifactId, Value: entityEx [INFO] Parent element not overwritten in /home/jcstaff/workspaces/ejava-javaee/git/jpa/jpa-entity/entityEx/pom.xml [INFO] project created from Archetype in dir: /home/jcstaff/workspaces/ejava-javaee/git/jpa/jpa-entity/entityEx [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.535s [INFO] Finished at: Sat Feb 09 23:04:10 EST 2013 [INFO] Final Memory: 15M/59M [INFO] ------------------------------------------------------------------------
You should now have an instantiated template for a JPA project
entityEx/
├── pom.xml
└── src
├── main
│ └── java
│ └── myorg
│ └── entityex
│ └── Auto.java
└── test
├── java
│ └── myorg
│ └── entityex
│ └── AutoTest.java
└── resources
├── hibernate.properties
├── log4j.xml
└── META-INF
└── persistence.xml
Verify the instantiated template builds in your environment
Activate the h2db profile (and deactivate the h2srv profile) to use an embedded file as your database. This option does not require a server but is harder to inspect database state in between tests.
relationEx]$ mvn clean test -Ph2db -P\!h2srv ... -HHH000401: using driver [org.h2.Driver] at URL [jdbc:h2:/home/jcstaff/workspaces/ejava-javaee/git/jpa/jpa-relation/relationEx/target/h2db/ejava] ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------
Activate the h2srv profile (and deactivate the h2db profile) to use a running H2 database server. This option provides more interaction with your database but does require the server to be running.
relationEx]$ mvn clean test -P\!h2db -Ph2srv ... -HHH000401: using driver [org.h2.Driver] at URL [jdbc:h2:tcp://127.0.0.1:9092/h2db/ejava] ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------
You may now import the instantiated template into Eclipse as an "Existing Maven Project"