In my design I've not used Stateful EJB, rather I've taken the conventional route of using Stateless EJB(s). I dont want to discuss the good or bad reasons why. My rationale was that stateless ejb will give me a good scalability quality attribute in my design esp. if there is a requirement to scale to upto 600 concurrent users.
What I want to know is regarding my assumption. Now since I'm not using a SFSB, My architecture does not seem to be fault tolerant. e.g if there is a network outage for a brief period of 5 secs, after I made my iternary and going to pay $ using credit card.
I know this can be achieved by storing the session information in a backend database against the userprofile and reusing it the next time. I dont have the time to show this again in my design with more diagrams as already my assignment has become huge.
if you dont use a SFSB you must think wich session managment techinque to use in both clients .... (reusability)
Santiago Urrizola : La Plata - Argentina<br />SCEA (89%-92%)<br /><a href="http://gpitech.wordpress.com/" target="_blank" rel="nofollow">http://gpitech.wordpress.com/</a>
Joined: Mar 27, 2006
"Stateful or stateless doesn't change anything regarding fault tolerance"
sorry i disagree with you. It does. SFSB stores state across method calls. Which means that when the client is unavailable and before the bean times-out, the bean is available. If you are able to locate the same bean back before the time-out happens, the container maintains the state of the bean. Which also means may be your reservation that was pending because you accidentally closed your browser is still available just like a shopping cart... that's what I meant by fault-tolerant in case of a client network outage for a brief duration.
Man these one liner answers really kill the whole idea of a forum !!