Seam emphasizes the use of stateful components.
Seam强调使用有状态组件。
An improved lifecycle for stateful components, bound to well-defined contexts.
改善有状态组件的生命周期，并绑定到定义良好的上下文上。
See the discussion on stateful components in the first article in this series to learn about the problems that data instability can cause with regard to queued events on a UIData component.
请参阅本系列第一篇文章中关于有状态组件的讨论，了解数据不稳定可能对UIData组件的列队执行事件所造成的问题。
Stateful components can be problematic in a web context because of managing cached state for example - many applications break when a rollback occurs because the state isn't tied to the transaction.
由于需要管理缓存着的状态，有状态的组件可能会在Web上下文中出现问题，比如，发生回滚时许多应用都会出问题，因为状态并没有和事务绑定起来。
To manage state on the business tier, we use stateful session EJB components.
要在业务层上管理状态，我们使用有状态会话ejb组件。
I am having a hard time imagining how I would do the same thing as simply without stateful session EJB components.
我思考了很久，如何能够在不使用有状态会话ejb组件的情况下完成相同的任务。
JS f组件是有状态的。
It is generally a good practice to encapsulate the data component with its data access business component. This is especially the case for stateful business components.
通常用数据访问业务组件封装数据是一项好的实践，特别是针对有状态业务组件。
All in all, stateful session EJB components provide a heavyweight mechanism for managing application state.
总而言之，有状态会话ejb组件为管理应用程序状态提供了一种重量级机制。
In GDS, I want to work on the concept of stateful server components, as defined for example, by the Seam conversation and task concepts.
我想在GDS中继续致力于有状态服务器组件的设想，比如说，就像由Seam对话和任务的设想所定义的一样。
Although some of the above questions seem to clearly lean to one technology over the other, many stateful scenarios actually call for the use of both servlets and EJB components.
尽管上述一些问题似乎明显地倾向于其中一种技术，但是许多有状态方案实际上既需要使用servlet 又需要使用 EJB 组件。
We also extended the notion of components to optionally be stateful.
我们还扩充了组件的概念，将stateful作为可选项。
As we will soon see, Seam components make it a breeze to develop stateful and transactional web applications.
我们很快就会发现，Seam组件使开发有状态的和有事务的web应用变得易如反掌。
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的池不能象无状态EJB组件的池那样用来容纳任何客户机请求。
One of the prime components of creating stateful applications is data management.
创建有状态应用程序的一个基本组成部分就是数据管理。
The scenarios discussed here don't cover every situation, but they are representative of some of the most common uses for servlets and session EJB components in a stateful communication context.
本文讨论的方案并未包含所有情形，但是它们代表了有状态通信环境中的servlet和会话EJB组件的一些最常见用法。
Wicket pages are components also, and their states are stored in the Wicket session if they are stateful.
Wicket页面也是组件，如果具有状态，则它们的状态将保存在Wicket会话中。
At the same time, Seam expands the EJB3 component model to POJOs and brings the stateful context from the web tier to the business components.
同时，Seam拓展了EJB3到POJO的组件模式，从we b层到业务层都有了状态上下文。
But beyond that we're also trying to write components that are both stateful and loosely coupled.
但是除此之外，我们还试图编写出既有状态又松耦合的组件。
But beyond that we're also trying to write components that are both stateful and loosely coupled.
但是除此之外，我们还试图编写除此之外我们规范出既有状态又松耦合的组件。
But beyond that we're also trying to write components that are both stateful and loosely coupled.
但是除此之外，我们还试图编写除此之外我们规范出既有状态又松耦合的组件。
应用推荐