Samson begins to echo Milton from the invocation that we've been looking at, the invocation to Book Three of Paradise Lost.
从我们一直看的祈祷，从《失乐园》第三卷中的祈求，参孙开始附和弥尔顿。
This is the invocation of an operation.
这是对操作的调用。
The invocation of a session bean method.
会话Bean方法的调用。
The invocation styles that SCA provides are.
SCA提供的调用样式有。
This is known as the invocation pattern.
这被称为调用模式。
Let's examine the invocation path and results.
现在我们将对调用路径和结果进行检查。
The invocation pattern is the last pattern.
调用模式是最后一种模式。
Invoked on denotes the invocation date and time.
InvokedOn表示调用日期和时间。
Figure 3 shows the result of the invocation.
图3显示了调用结果。
You will now see the result of the invocation.
现在您将看到调用的结果。
The one at the client side to make the invocation.
在客户端用于发出调用的事务。
Caller: the component that initiates the invocation.
调用者：发起调用的组件。
The result of the invocation of the selected service.
调用被选中服务的结果。
The invocation is basically unattended and synchronous.
这种调用基本上是无人值守和同步的。
But so far, I've only explored the invocation side.
但到目前为止，我还只是探讨了有关调用的内容。
Figure 13 shows the invocation model defined by JRules.
图13给出JRules定义的调用模型。
The invocation counts and the execution times for SQL calls.
对SQL调用的调用计数及执行次数。
The consumer can then choose the invocation model it likes best.
然后，使用者可以选择它最喜欢的调用模型。
The invocation of an external service returns an unexpected fault.
调用外部服务返回意外错误。
Takes the current time of the invocation request on the inbound.
获取对入站调用请求的当前时间。
Figure 3 summarizes the invocation scheme used in all of these cases.
图3总结了所有这些案例中使用的调用模式。
The invocation in SQL of the Easy mining Procedure for associations mining.
这个sql语句调用“简单挖掘过程”来进行关联挖掘。
The interesting part is the input types that are sent in/out of the invocation.
其中颇有意义的一部分是传入/传出调用的输入类型。
The process of wiring the invocation up to the implementation is called binding.
将调用和实现绑到一起的过程叫做绑定。
The invocation behavior of interface maps has changed from version to version.
各个版本间的接口映射的调用样式均已发生变化。
On the bottom frame, you should see the results of the invocation (Figure 20).
在底部框架中，您会看到调用的结果(图20)。
The invocation handler class is where all of the data validation logic is handled.
调用处理程序类是处理所有数据验证逻辑的地方。
This can be verified by the service class name printed with the invocation message.
这一点可以通过随调用消息输出的服务类名称得到验证。
As you can see, the invocation itself is actually the smallest part of the implementation.
您可以看到，这个调用本身实际上只占实现很小的一部分。
应用推荐