那么注解处理器将会产生业务接口。
The annotation processor will then generate the Business Interface.
清单2显示了完整的业务接口。
由业务委托接口提供的业务接口。
Business interface provided by the business delegate interface.
EJB 3.0引入了业务接口的概念。
EJB 3.0 introduces the notion of a Business Interface. An example is shown below.
业务接口是可选的，即使对于会话bean也是如此。
清单1显示了Library对象的一个简单的业务接口。
Listing 1 shows a simple business interface for a Library object.
这个业务接口明确地定义Library对象的业务用法。
The business interface clearly defines the business usage of the Library object.
每个服务或引用都有一个接口，将业务接口描述为一组方法。
Each service or reference has an interface that describes the business interface as a set of methods.
早期的草案中允许存在从bean类产生业务接口的可能性。
The early draft talks about allowing the possibility for the generation of Business Interfaces from the Bean class.
业务接口模式不是避免远程对象设计中不匹配的方法的唯一方法。
Note that the Business Interface pattern isn't the only way to get around mismatched methods in remote object design.
请阅读补充文章“业务接口模式的替代方法”以学习其它解决方案。
Read the sidebar "Alternatives to the Business Interface pattern" to learn about other solutions.
您也可以将此模式用于远程和本地接口（两者都继承了业务接口）。
You can also use remote and local interfaces (both extending the business interface) with this pattern.
EJB 3.0引入了业务接口概念，而非单独的远程和本地接口。
EJB 3.0 introduces the notion of a business interface, rather than separate remote and local interfaces. An example of this is shown below.
清单3显示：如果使用业务接口模式构建远程接口，它会是什么样子。
Listing 3 shows what the remote interface would look like if it were built using the Business interface pattern.
运行时连接是一个调用链集合；业务接口中的每个方法都有一个调用链。
A runtime wire is a collection of invocation chains; there is one invocation chain per method in the business interface.
有了合适的与 EJB 兼容的业务接口，下一步是在远程接口中扩展它。
With the EJB-compatible business interface in place, the next step is to extend it in your remote interface.
因此，Struts提供了它能够理解的一个业务接口，即 Action 。
Therefore, Struts provides a business interface it does understand, Action.
业务接口模式有希望能改变您对会话和消息驱动的bean进行思考和编码的方式。
Hopefully, the Business Interface pattern will start to change the way you think about and code your session and message-driven beans.
无接口视图：简化了EJB的编写，只需要一个Bean，无需再编写单独的业务接口。
No-interface view: This simplifies the creation of an enterprise bean using only a bean class without having to write a separate business interface.
本文设计和实现的功能主要包括全网短信业务接口模拟和基本信息管理等功能。
The main functions of design and realization include national SMS service interface simulation and basic information management function.
一个简化的本地视图，无需单独的本地业务接口就可提供sessionbean的访问。
A simplified local view that provides session bean access without a separate local business interface.
它也显示了对其它类的依赖性，如前面描述的两个模式中的marshaller和业务接口。
It also shows dependencies on other classes, our marshaller and the business interface, as described in the two previous patterns.
以上的@无状态注解，意味着此类现在是一个无状态会话bean，将使用业务接口来调用它。
Stateless annotation, above, means that this class is now a stateless session bean, and the business interface is used to invoke it.
最后，在调用业务接口中的每个方法时，作为参数提供给方法并从调用返回的数据将通过数据绑定提取。
Finally, as each method in the business interface is invoked, the data provided to the method as parameters and returned from the call is abstracted using a data binding.
此模式在框架接口、业务接口和UDDI服务注册等模块支撑下，为下一代网络提供新的运作模式。
Supported by the modules of frame interface, service interface and UDDI service registration, this mode provides a new operation mode for the Next Generation Network.
然而，在业务接口模式下，实现类还将需要实现新的业务接口(在这种情况下，是ILibrary接口)。
Under the business interface pattern, however, the implementation classes will also need to implement your new business interface (in this case, the ILibrary interface).
这个新版本有一些新功能，公司内部的一个新应用程序需要这些新功能，而且很自然地扩展了EJB组件的业务接口。
This new version has some functionality that a new application internal to the company needs and, naturally, extends the business interface for its EJB components.
JBoss曾经有一个概念是EJB的SecurityProxy，您可以在其中提供EJB业务接口的实现，该实现可以在代码中执行这些安全检查。
JBoss used to have a concept of SecurityProxy for EJBs, where you could provide an implementation of the EJB business interface that could execute these security checks in code.
CustomerProcess是面向后端系统的业务接口，使用ESB中介对BusinessEvents系统生成的操作进行转换之后，将由后端系统进行处理。
CustomerProcess is the business interface to the back-end system that will process the actions generated by the business Events system once they've been transformed using the ESB mediation.
此时，我们已经创建了标准的接口和业务对象。
At this point, we have created standard interfaces and business objects.
应用推荐