posted 19 years ago
Steven,
The reason why I want to use a DAO there is because, the prices can change ANY time. So when the customer selects the itinerary, the segment prices are not yet displayed (most of the online booking sites work the same way). It's only when the user confirms the seat does it actually go and get the latest price.
This is just a little idea that I put in my work, but I am sure you can design it it anyway you want. But still I am concerned about the number of components in that SD.
Ajai and Steven.. how many components do u have in price Itinerary SD ???
SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCEA