Also added explicit names for foreign key constraints to mapping files.

More flesh on RouteSpecification, with some ideas around factory methods for specifications.

Renamed a few service methods to match ubiquotous language more closely.

Pushed DTO assembly outside of service layer and into MVC controllers, pending creation of dedicated remoting layer. Service layer now uses pure domain model classes.  

CarrierMovementId implements ValueObject.

Persistence annotations removed from domain model classes.

DeliveryHistory is now immutable.

Domain model implements the new pettern interfaces (entity/value object/domain event)

Orphaned old itinerary is now deleted when attaching a new itinerary to a Cargo.

Implemented orphan delete of the old itinerary when a new itinerary is attached to a cargo.

Changed the addEvent mentod of CargoTrackingDTO to take strings instead of a DTO.

Optimized imports.

Misc CheckStyle fixes.

Removed magic numbers from HashCodeBuilder.

Created a separate sub package for DTO assemblers.

Minor refactorings to increase readability.

Started work on external DTO assembler.

Package-level javadoc effort begun.

Better timestamps in sample cargo data.

Removed unneeded constructors in Cargo and UnLocode.

Fixed spelling error in StatusCode - "e before i except after c", or whatever that was :-)

Cascade Itinerary/Leg on Cargo persist.

Cargo registration and routing web administration interface.

Better randomization in RoutingServiceImpl.

Replaced more test locations with the SampleLocations instances.

Reorganized JSP views slightly.

Introduced Itinerary.EMPTY_ITINERARY to represent an emtpy itinerary (null object pattern)

Added capability to display expected/misdirected status of cargo and events to web tracking interface (jsp, DTOs, etc)

Location constructor now only has package-level visibility, and test code uses static location instances.

Rewrote UN Locode import to use straight JDBC access.

Two different implementations a available: JMS and a simple thread-based one.

Also, the cargo service track method now uses TrackingId in the signature, for consistency.

Entities have the method sameValueAs(otherEntity)
Value Objects have the method sameIdentiyAs(otherValueObject)
Events have the method sameEventAs(otherEvent)