Meaningless Drivel is fun!*
The moose likes EJB and other Java EE Technologies and the fly likes When the client makes its second call to the stateful session bean, how does that bean know it is co Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "When the client makes its second call to the stateful session bean, how does that bean know it is co" Watch "When the client makes its second call to the stateful session bean, how does that bean know it is co" New topic
Author

When the client makes its second call to the stateful session bean, how does that bean know it is co

Aalok Singh
Greenhorn

Joined: May 27, 2010
Posts: 14
Hello Ranchers,

Exactly how is the state retained from client to application server?
In other words: when the client makes its second call to the stateful session bean, how does that bean know it is coming from that same specific client?

Here what is client... servlet or logged in user..?


Regards,
Aalok
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 9955
    
163

The "session" is maintained in the proxy that's returned to the code which either does the lookup of the bean or gets the bean via injection. As long as you use the same proxy instance, the session info is retained and is available to the server to identify it to a session state.

Here what is client... servlet or logged in user..?


Any code which is using that bean.


[My Blog] [JavaRanch Journal]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: When the client makes its second call to the stateful session bean, how does that bean know it is co
 
Similar Threads
HFEJB p.561: Help needed to fill Exception Chart for Remote and Local Clients
EJB Timed out
Doubts in Serializing the Session bean methods
Doubt in mock exam Qs from HFEJB
How is Stateful session bean mapped to Client