I decided to add to this
thread as I was wondering a similar thing
See I am in the process of writing a system which (again) contains a shopping basket and stuff. I'm looking at EJB3.0 mainly because I've used EJB2.1 before and am familiar with the structure (although 3.0 has changed
alot to 2.1... for the better)
But I got to thinking, do I need Session beans? The shopping cart isn't such a bad thing because of the actual transaction when the user is ready to hit the 'BUY' button.
But i also have a Stateful Session bean that holds the users details (name, email, address, telno, etc). Now my original system used a standard JavaBean held in the HttpSession, I then changed it to use a Stateful Session Bean (collects the information on login).
The thing is, I've designed my system with seperate Presentation(
JSP,
Servlets) and Business(EJB-3.0) layers. Now everytime I call say .getName() or .getEmail() i will be making TWO remote calls accross the network from one server to the other and back, this will obviously become a very heavy load if I have say 1,000 on at the same time!!!
I then thought "Hmmm maybe I'll make one call, send the data from the Busness end (via DB query) to the Presentation server and store it in a standard Bean". Then I realised that this would defeat the point of using Session Beans!
So basically I'm guessing it's not recommended to use REMOTE Session Beans for somethign like UserDetailsBean (name, address, etc).