ejb
- 网络资源(Enterprise Java Beans)；的设计模式和命名约定；部署
ejbejb
资源(Enterprise Java Beans)
在J2EE里，Enterprise Java Beans(EJB)称为Java 企业Bean，是Java的核心代码，分别是会话Bean（Session Bean），实体B…
的设计模式和命名约定
EJB概述(下) _天极网 ... System Administrator 系统管理者； EJB 的设计模式和命名约定： Application Assembler 程序组装器: ...
部署
目录 - EJB JPA - 博客频道 - CSDN.NET ... 3.3.1 依赖注入 EntityManager 3.4.2 部署 EJB 4.1.1 什么是 Dali JPA ...
的部署
Java Web整合开发王者归来_百度百科 ... 34.2.2 JBoss 的目录结构 764 34.3.4 EJB 的部署 769 35.1.1 JPA 的出现 776 ...
容器
Java程序设计之网络编程_百度百科 ... 17.2.5Servlet 应用举例 18.2.1EJB 容器 19.2.5JINI 技术 ...
1
A small number of changes to the application code is often required to change the format of names used for EJB lookups.
经常需要对应用程序代码作小量改动以改变用于EJB查找的名称格式。
2
However the specification has a dependency on EJB (or at least EJB Lite) which seems to limit its wider applicability.
但是，规范依赖EJB（或者至少是EJBLite），这限制了它的广泛应用性。
3
In fact, avoiding this style of coupling was one of the motivating factors behind the creation of Enterprise JavaBeans (EJB) technology.
实际上，避免这类耦合是创建企业JavaBean（EJB）技术背后的一个动机。
4
Now that you've seen this relationship, you're ready to examine the sections left out of the EJB DD above.
既然您已经知道了这个关系，那么可以研究上面的EJBDD中没有讨论过的节。
5
How much of EJB version 1. 0 technology is still alive?
有多少1.0版的EJB技术仍有生命力？
6
Each EJB 3 business interface with the unqualified name intf of a session bean bean translates into a service by the name bean_intf.
带有一个会话beanbean的非限定名称intf的每个EJB3业务接口都转换为一个名为bean_intf的服务。
7
A similar approach is to use one of Spring's abstract EJB implementation support classes as a base class for your EJB implementation.
一种类似的方法是使用Spring的抽象EJB实现支持类之一作为EJB实现的基类。
8
In the above example, the injected value for sbean2 would be that of the SCA reference sbean2 and not the EJB reference of the same name.
在上面的示例中，sbean2的注入值将是SCA引用sbean2的注入值，而不是相同名称的EJB引用。
9
Depending on where the client is located relative to an EJB, it is possible to set the best way of access to the bean's logic.
取决于客户端与EJB的相对位置，可以设置访问Bean的逻辑的最佳方式。
10
If you can answer _yes_ to any of these questions, then EJB components may be an appropriate technology in your situation.
如果你对所有这些问题的回答都是肯定的话，那么EJB组件就是你可以采用的合适技术。
11
EJB components do not look like its Object Oriented as it has restrictions for using inheritance and polymorphisms.
EJB组件不像是面向对象的，比如在使用继承和多态时就有太多限制。
12
As long as the interface of the SCA reference matches that of the EJB reference, the SCA run time injection will override that EJB.
只要SCA引用接口匹配EJB引用接口，SCA运行时注入将替换那个EJB。
13
These terms are all about locations - the conceptual location where EJB components are available , from the point of view of your client .
这些术语都是有关位置的是从客户机的角度看时EJB组件所在的概念性的位置。
14
In EJB development, the Session Facade pattern is often used to minimize network traffic and ensure transaction consistency.
在EJB开发中，会话虚包（SessionFacade）模式常被用来使网络流量最小化和确保事务一致性。
15
In previous Java EE platforms, such a descriptor would have been a part of an XML file that conforms to the EJB 2. 1 schema.
在以前的JavaEE平台中，必须在一个符合EJB2.1模式的XML文件中包含这样的描述符。
16
Interestingly, a Seam conversation is typically implemented with an extended entity manager injected into a stateful session bean (EJB).
有趣地是，Seam对话通常用注入到有状态会话bean（EJB）中的扩展的实体管理器实现。
17
Any object that can be returned by an entity bean (or any other EJB component) must fulfill this requirement.
任何可以被实体bean（或任何其它EJB组件）返回的对象都必须满足这个要求。
18
The modified EJB is now ready to be transferred to Integration Edition.
修改过的EJB现在可以被转移到集成版了。
19
Conversely, imagine a business process that needs to call out to an already existing EJB service.
从相反方面考虑，可以假设业务流程需要调出到现有EJB服务。
20
There may be other issues with the EJB specification I could attack, but these five have been bothering me for quite some time.
EJB规范中或许还有其他问题，但是这五个问题已经困扰我很长时间了。
21
Another possibility is to invoke an EJB component as though it were a CORBA component.
另一种可能性是调用EJB组件，就好象它是CORBA组件一样。
22
It would be nice if I could apply container services one time across many EJB definitions.
如果一次能在许多EJB的定义中应用容器服务，这样情况会好些。
23
In the other, EJB component use resulted in an excessively complicated system that did not perform well.
在另一个例子中，使用EJB组件使得系统过于复杂，性能也不好。
24
However, you will have to be aware of a few rules and design considerations to avoid treading on the EJB specification.
然而，必须了解一些规则和设计考虑，以免破坏EJB的技术要求。
25
It should be noted that you can change the multiplicity as well as the role names of the EJB relationship from within the diagram.
应当注意到您可以在图表中改变多样性及EJB关联角色的名称。
26
Calls to the optimized local adapter invocation or send request APIs do not result in an inbound JCA request to drive into the target EJB.
针对优化的本地适配器调用或发送请求API的调用不会导致入站JCA请求以便进入目标EJB。
27
Next time you take a POJO and slap on an annotation to turn it into an EJB, you can give a little thanks to the OpenEJB team.
下次当您给POJO加上一些注释将其转换成EJB时，您应对OpenEJB团队所作的贡献表示感谢。
28
Chief among these criticisms was that EJBs were difficult to understand and tedious to develop.
在这些批评之中，最主要的抱怨是EJB难于理解且开发起来繁琐乏味。
29
These services can be implemented as remote Enterprise JavaBeans (EJB) method calls, web services, or CORBA calls, just to name only a few.
这些服务可以作为远程企业JavaBean（EJB）方法调用、Web服务或CORBA调用（这里只列出几个）来执行。
30
Until the advent of EJB technology, there was no way to restrict access to an object or method by a particular user.
直到EJB技术出现后，才能够限制特定用户访问某个对象或方法。