This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Dear all ranchers, I'm almost done with my part II architecture. I have a doubt about the persistence of the Flight Itinerary. Once you have created your Itinerary, should it be moved to a persistent storage ? this way if you return to the site next day you can edit it or pay for it ......?
I don't see this in the requirements, so I'd like to hear to opinion of other ranchers about it.
Taking a trip on some travel agency sites made me lead for a Session storage of the Itinerary (in the SFSB), instead of persisting it on the DB. In fact I see not many companies have chosen to keep track on the DB of travellers itineraries......
There are ambiguities to the exam in order to allow you latitude in how you solve the problem. You are being tested not only on your knowledge of Java, but also on your problem solving ability. If you are uncertain of how to do something, document heavily in that section. The main idea is to ensure the project works, and to document the choices you have made.
Well thanks for your reply. Anyway I'd be grateful if somebody could provide feedback about my approach. Do you think it's correct to store the Itinerary in the Session ? or better on phisical storage ? Thanks Francesco