The idea is that one entity wants to initiate communication to another entity, and sends an INVITE to a communication session (Figure 1).
其想法是这样的，一个实体希望发起与另一个实体的通信，并向通信会话发送一个INVITE(图1)。
Remote interfaces to session or entity EJB components provide location independence.
会话或实体e JB组件的远程接口提供了位置独立性。
Session EJBs behave essentially the same as entity EJBs when it comes to deployment.
在部署时，会话ejb需要的工作实际上与实体e JB相同。
The scenarios discussed here don't cover every situation, but they are representative of some of the most common uses for entity EJB components and session EJB components.
这里讨论的方案并未涵盖所有情形，但是它们代表了实体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.
简而言之，如果您想接收位于会话外观后的本地实体eJB，您也要接收位于其后的本地有状态会话ejb。
Session beans typically operate on one or more entity beans.
会话bean通常会操作一个或多个实体bean。
Entity beans are also typically accessed through session beans, which means each transaction involves at least two enterprise beans and often many more.
实体bean通常也可以通过会话bean来访问，这意味着每个事务至少包含两个企业bean，而通常会更多。
Therefore, Entity EJBs accesses in any business method of the session bean AccountManagement are executed in a global transaction.
因此，访问会话BeanAccountManagement中的业务方法的实体e JB都在一个全局事务中执行。
Session beans and entity beans can send JMS messages, but can only receive them synchronously.
会话bean和实体bean可以发送JMS消息，但只能同步接收这些JMS消息。
In this third installment of the J2EE pathfinder series, we have compared and contrasted entity beans with session beans and JDBC for data persistence.
在J2EE探险者系列的第三部分中，我们针对数据持久性将实体bean与会话bean和jdbc组合作了比较和对照。
This sample project consists of an entity bean, a session bean, a sample servlet, and a sample client.
这个样本工程由一个实体bean、一个会话bean、一个样本servlet和一个样本客户机组成。
First, to avoid network overhead and force adherence to business rules, entity beans are almost always accessed through a session bean.
首先，为了避免网络开销并强制遵守业务规则，几乎总是通过会话bean访问实体bean。
Upon receiving a message, the client could then establish a synchronous RMI connection with the application server and invoke the session or entity beans in the usual way.
当收到一条消息时，该客户机便可以与应用服务器建立一个同步的RMI连接，并按照常规的方式调用会话bean或者实体bean。
Location independence is provided by remote interfaces using RMI over IIOP to stateless session beans or entity home methods that encapsulate the services.
位置独立性是由远程接口使用RMIover IIOP提供给无状态会话Bean或封装服务的实体home方法的。
In this article we discuss the different options available to secure session, entity and message-driven EJBs using Community Edition.
在本文中，我们将讨论可使用CommunityEdition来保护会话、实体和消息驱动的EJB的不同选项。
This will pass execution on through to the servlet controller to the session bean on to the entity bean.
这将使执行转移到servlet控制器，然后转到会话bean，再转到实体 bean。
A session bean accessing multiple entity beans is much more efficient and easy to maintain than allowing clients to make multiple remote method calls.
一个会话bean访问多个实体bean比允许客户机进行多次远程方法调用效率要高得多，维护起来也要容易得多。
Unlike session and entity beans, message-driven beans are not invoked by other beans or client applications.
与会话Bean和实体Bean不同，消息驱动的Bean不会由其他Bean或客户端应用程序调用。
Overall, the system redesign minimized network traffic by using session beans that were deployed with entity beans.
总之，通过使用与实体bean一起部署的会话bean系统重新设计使网络流量最小化。
The new session bean makes calls to the entity beans on the server on behalf of a client.
新的会话bean代表客户机对服务器上的实体bean进行调用。
For example, we will put entity and session beans into different JARs, since larger J2EE applications are often comprised of several JARs, or projects.
例如我们将把实体Bean和会话Bean放在不同的JAR中，之所以这样做是因为较大的J2EE应用程序常常是由若干JAR或项目组成的。
Two types of EJB technology are entity beans and session beans.
EJB技术的两种类型是实体bean和会话bean。
The SnippetsEJB project contains one entity bean, and four session beans.
SnippetsEJB项目包含一个实体bean和四个会话bean。
But that previous column leads one to question whether a session bean is necessary at all, introducing the possibility of using entity beans and their Home methods instead of session beans.
但上期专栏介绍了使用实体Bean及其Home方法代替会话Bean的可能性，从而使人们对会话Bean是否真的是必需的产生了疑问。
Unlike entity beans, stateless session beans have not ridden a roller coaster of popularity (see sidebar).
无状态会话bean的受欢迎程度不象实体bean那样大起大落(请参阅侧栏)。
The app.jar file contains all EJB3 bean classes (both entity beans and session beans), as well as EJB3 related configuration files.
jar文档包含所有的EJB3bean类（实体bean和会话bean）以及EJB3相关的配置文档。
The max-beans-in-free-pool element defines the maximum size of the free pool of EJBs for a specific entity bean, stateless session bean, or message-driven bean.
max - beans - in -free -pool元素定义了特定实体bean、无状态会话bean或消息驱动bean的ejb空闲池的最大大小。
Then, Seam passes the entity bean into the event handler session bean, which is also created by Seam, for processing.
然后，Seam将实体bean传入同样被Seam构造的事件处理器会话bean中来处理。
Prior to the EJB 2 specification it was always considered best to use a session bean facade around an entity bean.
在EJB2规范之前，总是认为在实体Bean周围使用会话BeanFacade是最佳的。
Access session and entity beans asynchronously.
异步地访问会话bean和实体bean。
应用推荐