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.
I need to know somethings about N-tier web applications.
Actually what I need is to know is how context listeners, session listeners work with them(and others too). Like in a N-tier application does it share same context attributes or how sessions work with it etc...
Reason I’m asking this is I got to know that in SCWCD 5 they are asking something similar things like this.
Thanks in advance.
Well Amila, when your application is deployed on a distributed environment, the session information will transfer remotely to other JVMs in the same environment. In this case, session information should have to be serialized and deserialized in order to pass it as a remote object. Hence you should care about HttpSessionActivationListener an must implement it's sessionDidActive and sessionWillPassivate methods appropriately if it is needed. It is required to do so, if the session stores some connections pooling data / or resources which must be committed and/or closed before serializing them. For the SCWCD exam you are NOT expected to have a deep knowledge about distributed environments. Instead of that, basic understanding about HttpSessionActivationListener is sufficient for the exam. And keep in mind that multi-tier (n-tier) architecture is completely differ than distributed environments.