使业务方法抛出运行时的异常。
我采用POJT对域模型类的业务方法进行测试。
I tested the business methods of domain model classes with POJTs.
在域对象中，您可以把相同的推理应用到业务方法。
You can apply the same reasoning to business methods within domain objects.
同样，可以在一个业务方法中打开并管理多个事务。
Likewise, multiple transactions can be opened and managed within a single business method.
在样本应用程序中，业务方法展示了达到的事件的内容。
In the sample application, the business methods display the contents of the arrived event.
首先，需要编写一个定义所有业务方法的接口。
First, you need to write an interface that defines all of your business methods.
因此，它们可能包含此处没有描述的一些业务方法的调用。
Therefore, they may contain invocations of business methods that are not described here.
这也简化了筛检、早期发现和有针对性采取干预措施的业务方法。
Again, this simplifies the operational approach to screening, early detection, and the targeting of interventions.
这就是把域对象中的业务方法数量限制为必要的最少数量的理由。
That's why it might make sense to limit the number of business methods in domain objects to a necessary minimum.
返回的远程会话bean用于调用 bean的业务方法。
The remote session bean is returned to be used to call the bean's business methods.
鉴于这篇文章的目的，只为J2Cbean定义了一个业务方法。
For the purposes of this article, define only one business method for J2C bean.
这个业务方法添加在一个远程的接口中，使客户能够访问这个方法。
This business method is added to a remote interface to give clients access to this method.
它们提供了一些方法来让测试控制这个虚构类的所有业务方法的行为。
They provide methods to let the tests control the behavior of all the business methods of the faked class.
会话外观e JB业务方法调用了一个以上的DAO来将其保存在一张以上的表中。
A session facade EJB business methods call more than one DAO to save on more than one table.
面对这些严重疾病，我们面临着巨大挑战，因此，我们必须想方设法简化业务方法。
Anything we can do to simplify the operational approach is so important because the challenges, like the diseases themselves, are huge.
这没有什么特别的地方——因为保存应用程序状态的代码和几个业务方法与视图无关。
There's nothing special there — just the code to hold the state of the application and a few business methods having nothing to do with the views.
随后您可以使用getBean方法来获取相关的bean，并调用其业务方法。
You can then use the getBean method to get the relavant bean and invoke its business methods.
这些是共同的风险因素，为简化业务方法提供了方便。可以通过预防工作减缓这些风险因素。
These risk factors are Shared, which simplifies the operational approach, and they can be modified, which opens the prospects for prevention.
大多数业务方法都包含验证逻辑，以确保在执行业务逻辑之前，前提条件得到满足。
Most business methods contain validation logic to ensure that pre-conditions are met before carrying out business logic.
将下面三个业务方法添加到HelloWorldBean中，并将它们扩展到远程接口中。
Add the following three business methods to the HelloWorldBean and then promote them to the remote interface.
对跨多个业务委派中的多个业务方法使用相同的数据类型作为参数，这是十分常见的。
It's quite common to have the same data type used as an argument to multiple business methods, across multiple business delegates.
并且，它在多个层次上鉴定业务方法、流程和解决方案的可靠性，从而有助于推动资产鉴定工作流程。
And, it identifies business process, flows, and solution dependencies at multiple levels to help drive the asset identification workflow.
可以在您所有的portlet服务业务方法中使用以上的方法来调用远程Web应用程序。
You can use the above methods in all your portlet service business methods to make calls to the remote Web application.
因此，将portlet设置在调用任何业务方法之前的方法添加到portlet服务中。
Therefore, you add methods to the portlet service which the portlets set prior to calling any of the business methods.
本文余下的部分将解释这些技术如何交互，从而使您理解从服务调用到实现中的业务方法调用这一底层路径。
The rest of this article explains how these technologies interact so you can make sense of the underlying path, from service call to an invocation of a business method in an implementation.
清单2示例展示了业务方法在bean管理事务的情况下是如何实现的(注意，为简化起见省略了异常处理)？
Listing 2 is a sample of how a business method can be implemented in case of a bean-managed transaction (note that exceptions handling is omitted for simplicity)?
因为在Library接口中定义了所有的业务方法，所以实际上不必将任何新方法添加到远程接口。
Because all of your business methods are defined in the Library interface, you actually don't need to add any new methods to the remote interface.
假定取用清单1中的EJB，并用容器托管的事务部署它，将业务方法的事务属性设定为RequiresNew。
Suppose you take the EJB from Listing 1 and deploy it using container-managed transactions and a transactional attribute of RequiresNew for the business method.
其业务方法对应于顾客业务对象动词，并且允许通过使用J2EE编程模块来调用VTConnector。
Its business methods correspond to the Customer business object verbs and allow the invocation of the VTConnector using the J2EE programming model.
这样做的优势在于，只需将重点放在编写组件类中的业务方法上，而由Spring配置文件处理组件的生命周期。
The advantage is that you only focus on writing business methods in your component class and let the life cycle of the component be handled by Spring configuration files.
应用推荐