ascandroli / petstore Goto Github PK

is it possible to detect the hibernate "validate" error during startup.
It would be wonderful to avoid the validate error that prevents the app from running and then show the user some nicely formated error page like the one in Play Framework's Evolutions:

http://www.playframework.org/documentation/2.0/Evolutions

The Production execution mode is missing in the configuration. Add it!

Create the entities classes for the data model following the ERD createdpreviously.

Configure failsafe maven's plugin in order to execute UT in default's maven's phase (test) and execute IT in integration's maven's phase

Create the initial project using the Amneris's tynamo-archetype.
You will need to checkout the project and install the archetype in your local .m2 repository

Then execute:

mvn archetype:generate \
    -DarchetypeArtifactId=tynamo-archetype \
    -DarchetypeGroupId=org.amneris \
    -DarchetypeVersion=3.0.0-SNAPSHOT \
    -DgroupId=org.amneris \
    -DartifactId=petstore \
    -Dpackage=org.amneris.petstore \
    -Dversion=0.1.0-SNAPSHOT

After that, verify it works with: "mvn jetty:run -P commons,dev.local" and then check the code into github :P
Welcome to the Tynamo PetStore!!!

There is two custom blocks missing from the AppModule configuration.

As Pierce pointed out [1] in the tynamo mailing list, the MyDomainObjectResource example is not working.

[1] http://markmail.org/message/hp7sbdutbavnviqh

:)

Add the beanstalker maven plugin to allow easy deploy to AWS.

The current configuration based on maven profiles requires a rebuild to switch the configuration between environments.
Remove the maven profiles and start using Tapestry's ExecutionModes, so that the same war could be easily deployed to different environment.

info:
http://tapestry.apache.org/configuration.html#Configuration-SettingExecutionModes

Create persistence tests for all the entities.
Related info:

• Basic DAO-"Service"-Test-Setup
• help with tapestry hibernate
• How to unit test a DAO service with tapetsry-hibernate module

Refactor de model Entities.

Java properties should follow Java and Java Beans naming conventions:

• http://java.about.com/od/javasyntax/a/nameconventions.htm
• http://docstore.mik.ua/orelly/java-ent/jnut/ch06_02.htm

JPA Annotations and SQL should follow RoR naming conventions:

Columns

Columns are named where all letters are lowercase and words are separated by underscores, e.g. order_amount, total

Database Table

Table names have all lowercase letters and underscores between words, also all table names need to be plural, e.g. invoice_items, orders

Primary Key

The primary key of a table is assumed to be named id.

Foreign Key

The foreign key is named with the singular version of the target table name with _id appended to it, e.g. order_id in the items table where we have items linked to the orders table.

Many to Many Link Tables

Tables used to join two tables in a many to many relationship is named using the table names they link, with the table names in alphabetical order, for example items_orders.

Automated Record Timestamps

You can get ActiveRecord to automatically update the create and update times of records in a database table. To do this create two specially named columns created_at and updated_at to your table, i.e. t.datetime :created_at and t.datetime :updated_at. If you only want to store the date rather than a date and time, use :created_on and :updated_on.

source: http://itsignals.cascadia.com.au/?p=7

The SampleIntegrationTest has a little tiny BUG, fix it :)

Create an ERD diagram.

Missing properties messages for Signin