I guess my real question boils down to this : isn t it " crying wolf " to return dtos from entity cmps when you recommend using local interfaces to entity ejb components anyway 我想，我真正想问的是：您在建议使用实体ejb组件的本地接口时，从实体cmp返回dto是否是在“喊狼来了” ？
Therefore , i had a team test the performance and found to my happy surprise that there is no appreciable difference between the " client " calling a local get 因此，我让一个团队进行了性能测试，结果我很惊喜地发现，只要客户机和实体均位于同一个全局事务范围内， “客户机”通过本地接口调用本地get
The local interface and home to the same bean implementation would expose the create and find methods along with the appropriate get and set methods that possibly represent cmrs as described in 相同的bean实现的本地接口和home将公开create和find方法以及适当的get和set方法（它们可能代表cmr ，如
In a few simplified examples , this paper describes key java native interface programming concepts and highlights linux on power - specific , as well as common , programming pitfalls , where appropriate 本文通过一些简化的示例描述了重要的java本地接口（ java native interface ， jni ）编程概念，并在适当的地方着重指出了特定于power上linux的以及通常的编程隐患。
Just as significant , we saw the importance of using a data transfer object now being called an sdo and custom methods on entity ejbs to minimize the chattiness between layers , even when the local interface is used 更有意义的是，我们看到了在实体ejb上使用数据传输对象（现在称为sdo ）和自定义方法的重要性，其最小化了不同层之间的隔阂，即便在使用本地接口的时候也是这样。
If this hypothetical application directly uses the native interface of a particular relational database management rdbm system , switching to a new rdbm system involves reworking all the code that talked to the old system 如果这个假设的应用程序直接使用特定的关系数据库管理（ relational database management ， rdbm ）系统的本地接口，那么转换到一个新的rdbm系统将包括重写所有与旧系统进行对话的代码。
This article is useful to developers who are new to java native interface programming and want to test their jni programming skills on linux for power distributions , such as red hat enterprise linux 3 and suse linux enterprise linux v9 对那些刚接触java本地接口编程，并且想要在用于power的linux发行版本（比如red hat enterprise linux 3和suse linux enterprise linux v9 ）上检验其jni编程能力的开发者来说，本文会有所帮助。
Typically the collaboration templates for process flow logic and mediation logic will be tightly bound together at design time to form collaboration groups using the native interface provided by websphere interchange server , represented by a business object 通常情况下，用于流程流逻辑和中介逻辑的协作模板在设计时期将紧紧绑定在一起，使用websphere interchange server所提供的本地接口来组成协作组，通过一个业务对象来体现。
What s more , the pattern also provides a useful way to abstract away the details of the differences between local and remote interfaces in ejb 2 . 0 - rather than having to make your application programmers explicitly pick which home interface remote or local and which of the local or remote interface to use , you can abstract that detail away by hiding the decision behind a set of two business delegates 而且，该模式还提供了一种有用的方法来抽象出ejb 2 . 0中本地接口和远程接口之间的差别，而不必让您的应用程序设计人员显式地挑选使用哪一种主接口（远程还是本地）和本地或远程接口中的哪一个，您可以通过将决定隐藏在两个一组的业务代表的背后来抽象出细节。
But now that ejb 2 . x is here with local interfaces and cmrs , i have wondered about whether option a is the best we mentioned this offhandedly in the column on making entity ejb components perform , part 1 link - but we stuck to our guns that using custom dtos as described in option c is still best for the same performance reasons , though they are not nearly so acute 但现在已经推出了具有本地接口的ejb 2 . x和cmr ，我曾想过选项a是不是最佳的方法（我们刚在专栏文章making entity ejb components perform , part 1 ( link )中提到过这个问题）但我们始终认为，出于同样的性能原因（尽管它们可能不那么重要） ，使用选项c中描述的自定义dto仍然是最好的。
