|
|
@@ -31,13 +31,13 @@ import se.citerus.dddsample.domain.shared.Entity;
|
|
31
|
31
|
* of the cargo is contained in the Delivery value object, which is replaced whenever a cargo
|
|
32
|
32
|
* is handled by an asynchronous event triggered by the registration of the handling event.
|
|
33
|
33
|
*
|
|
34
|
|
- * The delivery can also be affected by routing changes, i.e. when a the route specification
|
|
|
34
|
+ * The delivery can also be affected by routing changes, i.e. when the route specification
|
|
35
|
35
|
* changes, or the cargo is assigned to a new route. In that case, the delivery update is performed
|
|
36
|
36
|
* synchronously within the cargo aggregate.
|
|
37
|
37
|
*
|
|
38
|
38
|
* The life cycle of a cargo ends when the cargo is claimed by the customer.
|
|
39
|
39
|
*
|
|
40
|
|
- * The cargo aggregate, and the entre domain model, is built to solve the problem
|
|
|
40
|
+ * The cargo aggregate, and the entire domain model, is built to solve the problem
|
|
41
|
41
|
* of booking and tracking cargo. All important business rules for determining whether
|
|
42
|
42
|
* or not a cargo is misdirected, what the current status of the cargo is (on board carrier,
|
|
43
|
43
|
* in port etc), are captured in this aggregate.
|