This is a situation where one might want to be more precise. A stateless
session bean does not maintain CLIENT state. But it can maintain state.
If you have a resource that is used for all clients, the stateless
session bean can keep and reuse that same resource across all client
invocations. For example, I have a stateless session bean that provides
directory services. Clients call the bean, the bean searches an ldap
directory, and returns the search result. This bean opens the ldap
connection when it is first invoked, and then reuses that same ldap
connection for all subsequent client requests. So, the bean has its own
state which is maintained across all client requests.
A stateless session bean does not maintain client state. The value
returned from getValue() will be indeterminate. Some folks on this list
have seen that sometimes one will get the same value that was set.
However, that is mere coincidence. Because the bean is stateless, the
container can send any method invocation to any instance of the bean.
The same instance that handled the setvalue may not handle the getvalue;
or several setvalue calls may all be handled by the same bean before the
getvalue is invoked.
"Peach, Joel" wrote:
>
> You are correct. Stateless session beans (SLSB) do not maintain state
> between method calls, per all versions of the EJB spec.
>
> From: pranav shah [mailto:[EMAIL PROTECTED]]
>
> if you will answer following of confusion then i will really apprceiate
> if i have a statelerss session bean and if i am setting the value of
> variable(say "name") by calling the method (say "setvalue").now when i will
> again call another method(say "getvalue") on the same bean object then the
> value of our variable "name" will be unknown.am i true ?
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
