Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

ListTO and EntityTO

 
Manny Pacman Pacquiao
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In paying the itinerary, part of the Use Case states something about displaying a "list of itineraries". Does this mean in the architecture(sequence diagram e.g.) we've to show usage of listTO and entityTO at least? I believe this would be good to show that the deliverable is utilizing the Composite Design Pattern or coarse/fine grain objects...
 
ManojKumar Unnikrishnan
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In displaying a list, am not sure, how a composite pattern would be used ?
I feel using a DAO would be a better option.
Is it necessary to use component based architecture or will POJO be fine ?
 
Ara Tatous
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can use ItineraryListTO. It's a transfer object, aka value object, that contains a list of ItinerayTOs.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic