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)

Brought Spring version back up to 2.5.1

Deleted hard coded dependency
Modified pom to assemble jar with dependencies

Allowed null carrier movement id to be passed into HandlingEventService.register().

A JAX-WS-based remote interface for registering events has been introduced, which works as an anti-corruption layer as well. 

CarrierMovementRepository uses Hibernate implementation, test class created.

Reverted to Spring 2.0.8 in order to get JAX-WS integration going, but that's only until the next release gets out.

Restored Cargo.lastKnownLocation() and Cargo.hasArrived().

All entities have sequential identifiers with no domain meaning. Equals and hashcode rely on business logic unrelated to persistence state.

Removed findDeliveryHistory from HaEvRepo since it's now OR-mapped.

Improved javadoc.

  Sample data is shared between testing and web application, and is loaded through a ServletContextListener

- No relation Cargo -> HandlingEvent, it only goes the other way. A HandlingEvent is only associated to one Cargo.

- TrackingId and CarrierMovementId do not rely on toString() anymore, the accessor for the id string is now called idString().

- CarrierId is now CarrierMovementId

- HandlingEventService now has named methods for registerLoad(), registerUnload() etc instead of the String "type" argument, which was extremely fragile.