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.
HI, Any stright forward answers for this question?.
J J Wright
Joined: Jul 02, 2008
I thought the Blueprints were pretty straight-forward!
188.8.131.52 Web-Tier State Recommendations
When using enterprise beans, it's best to maintain session state with stateful session beans in the EJB tier. For Web-only applications, maintain the state in the Web tier as session attributes (using HttpSession).
Well...thats where the confusion is...in some of the mock exams, it was quite clear Enterprise Beans was going to be used. But for some reason, Servlets were preferred to maintain the user sessions. It was not completely clear why...
Originally posted by ShreeRam Manivannan: HI, Any stright forward answers for this question?.
The straight answer is that you as architect decide which approach you are going to use, and justify that choice.
There may be a particular requirement that means you are driven to select one apporach over the other. If there isn't then you should be looking to justify your choice in terms of non-functional requirements.
None of the assignments have a single solution that you are expected to 'find', the examiners are looking for 'appropriate' choices and reasoned technical argument (expressed through your assumptions and design decisions) to back up those choices.
This applies to all the choices you make during the assignment - either there is a constraint within the information you are given that guides you down a route (stateless versus stateful, container managed persistence versus bean, etc) or there is not. When there is not you are expected to make an 'appropriate choice' and justify it in terms of the JEE architecture.
That is, after all, at the core of being a software architect.