There is also another case I forgot to mention: the cargo route can be re-specified, even if the effective origin remains the same mid-trip. In essence, the origin of the cargo and the origin of a given route specification assiged to the cargo are actually two different things.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
Date: 1/8/21 4:13 PM (GMT-05:00)
Subject: Re: [cargotracker-dev] design related question
Hi there,
The reason is that what is specified in the route and what actually happens during transport can vary. For example, the customer could have specified the route as NYC but actually drop off the cargo somewhere else but have the shipping company handle it anyway. The same can actually happen with the destination.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
Date: 1/8/21 3:53 PM (GMT-05:00)
Subject: [cargotracker-dev] design related question
Hi there,
Might be that this group is taking care only about porting CargoTracker on various jee technologies so apologize upfront and ignore my question is not relevant for the group.
Trying to understand the domain model and I see on That Cargo has the origin defined as Location but at the same time we have origin in the RouteSpecification which is part of Cargo.
My thoughts are that this information is immutable and still doubled once in Cargo and then in RouteSpec which belongs to Cargo.
May I ask why it was designed like this?
Thanks
Cristian
