隐藏域和有状态会话bean。
The three runner-ups are cookies, hidden fields, and stateless session beans.
有状态会话ejb组件的实现同样可以非常简单。
The stateful session EJB component implementation can likewise be very simple.
第三种备用方案是有状态会话bean。
该样例应用程序具有有状态会话bean。
有状态会话bean。
要在业务层上管理状态，我们使用有状态会话ejb组件。
To manage state on the business tier, we use stateful session EJB components.
使用有状态会话bean来提供有状态业务过程。
Use a stateful session bean to provide a stateful business process.
ejb容器提供了所有有状态会话bean管理。
The EJB container provides for all stateful session bean management.
有状态会话bean消耗了容器的大量时间和内存。
Stateful session beans consume a substantial amount of the container's time and memory.
相反，有状态会话bean与容器资源并不那样友好。
Stateful session beans, on the other hand, are not as friendly with the container's resources.
有状态会话bean保存特定客户机调用之间的信息。
A stateful bean preserves information between invocations from a specific client.
使用无状态会话Bean，而不是有状态会话Bean。
Use stateless session beans instead of stateful session beans.
有状态会话Bean是“最差”的实践或其他的什么情况吗？
使用有状态会话Bean，客户端的逻辑业务可能非常简单，如下所示。
With a stateful session bean, the business logic in the client can be as simple as.
相反，有状态会话bean并不是为这类应用程序而精心设计的。
Stateful session beans, on the other hand, are not well designed for such applications.
总而言之，有状态会话ejb组件为管理应用程序状态提供了一种重量级机制。
All in all, stateful session EJB components provide a heavyweight mechanism for managing application state.
使用应用程序服务器，该服务器为有状态会话bean的状态恢复提供自动支持。
Use an application server that provides automatic support for recovery of stateful session bean state.
与无状态会话bean一样，有状态会话bean也被映射到业务过程。
Like stateless session beans, stateful session beans are mapped to business processes.
一般情况下，有状态会话bean的开销要大于无状态会话bean的开销。
In general, the overhead for stateful session beans is greater than for stateless session beans.
似乎除了有状态会话Bean之外，您已经为所有的EJB组件类型找到了合适的用途。
It seems like you have found a good use for every EJB component type — other than stateful session beans.
我思考了很久，如何能够在不使用有状态会话ejb组件的情况下完成相同的任务。
I am having a hard time imagining how I would do the same thing as simply without stateful session EJB components.
有状态会话bean维护客户机的“会话状态”，适合处理那些跨越多个客户机请求的任务。
Stateful session beans maintain a "conversational state" with the client and are good for sets of related tasks that span multiple client requests.
此外，使用有状态会话Bean将会再添加一些状态到您的应用服务器上，这也是不好的做法。
In addition, the use of stateful session beans pushes state to your application server, which is undesirable.
有状态会话bean的池不能象无状态EJB组件的池那样用来容纳任何客户机请求。
A pool of stateful session beans cannot be used to accommodate any client request the way that a pool of stateless EJB components can.
这个服务密匙能够保证：一个指定的有状态会话bean将被来自同一个客户机的后续请求访问。
The service key can guarantee that a specified stateful session bean will be accessed by subsequent requests from same client.
IBMRecordsManagerAPI包含一些用于客户机的有状态会话bean。
The IBM Records Manager API comprises some stateful session beans for the client’s usage.
简而言之，如果您想接收位于会话外观后的本地实体eJB，您也要接收位于其后的本地有状态会话ejb。
In short, if you are willing to accept local entity EJBs behind a session facade, you should be willing to accept a local stateful session EJB behind one as well.
在J2EE应用程序中存储服务器端状态的其他方法是使用有状态会话bean，或者在数据库中存储会话状态。
The other alternatives for storing server-side state in J2EE applications is to use stateful session beans, or store conversational state in the database.
这些服务是DynaCache、内存到内存会话复制、核心组、Web服务缓存和有状态会话Bean持久性。
Those services are DynaCache, memory to memory session replication, core groups, Web services caching, and stateful session bean persistence.
与servlet不同，有状态会话bean不需要任何特殊的对象，也不需要使用额外的接口来创建有状态连接。
Unlike servlets, stateful session beans do not require any special objects or the use of an additional interface to create stateful connections.
应用推荐