图48显示调用checkin服务的结果。
图35显示调用checkin服务之后的结果。
Figure 35 shows the result after calling the checkin service.
然后创建一个显示调用备用源顺序的列表。
Then create a list that shows the order in which the alternate sources are invoked.
这个buffer显示调用堆栈，对当前frame反色显示。
This buffer displays the call stack, with the current frame displayed in inverse video.
每个条目显示调用函数的次数和关于函数调用的处理时间的统计数据。
Each entry shows the number of times that the function was called and statistics on the processing time for the function call.
“显示调用堆栈”链接，这将进一步扩展此错误以显示调用堆栈。
Show call stack link, which further expands the error to show the call stack.
然后您就可以往该文件夹中显示调用结果的任意页添加dtml字段。
Then you can add a DTML field into any page in the folder that displays the result of that invocation.
部分显示调用SimpleSessionBean中的每个方法的结果。
The EJB2.1 section shows the result of invoking each of the methods in SimpleSessionBean.
清单5显示调用了清单3中的advice方法，但是没有提供关于所执行的应用程序的很多有用信息。
Listing 5 shows that the Listing 3 advice methods are being called, but doesn't present much useful information about the application being executed.
正如显示HTML表单一节中所提到的，HTML表单片段中的按钮必须包含对submit函数的显示调用。
As mentioned in the Displaying the HTML form section, buttons in the HTML form fragment must include an explicit call to the submit function.
显示调用上下文（call context）：在序列图中，当鼠标在调用（call）上悬停的时候，就会弹出提示框，显示出调用上下文——调用方法的参数和返回值。
Shows call context: In the sequence diagram when the mouse is hovered over a call, the tooltip shows the call context - the call argument and the return value.
因为在其执行之后才显示这个系统调用，所以先输出了它的执行结果。
Because the system call is displayed after it has been executed, the output is shown in the line before.
这会显示出问题的调用。
图3显示了调用序列。
图5显示了侦听的调用序列。
它允许开发人员通过显示所有调用或一个选定方法的调用，来探索代码的执行路径。
It allows developers to explore a code execution path by showing all calls to, or calls from, a selected method.
清单3显示的是如何调用该方法。
大约一年之后，我增加了对显示与调用所有属性和方法的支持。
About a year later, I've added support for all properties and method display and invocation.
您可以选择调用栈中的条目，这样可以显示变量被调用时的值。
Entries on the call stack can be selected, causing variables at the time of invocation to be displayed.
图2显示了服务调用的流程。
图21显示使用JMS调用规则集的模型。
Figure 21 shows the model for invoking the rule set using JMS.
显示在调用结点上的操作
strace显示这些调用的参数并返回符号形式的值。
Strace displays the arguments to the calls and returns values in symbolic form.
图21显示了调用该功能生成的示例代码。
Figure 21 shows a sample code that might be produced from invoking this option.
图50显示，在调用checkout服务之后，附件内容成为原始附件数据。
Figure 50 shows that the attachment content becomes the original attachment data after calling the checkout service.
DB 2ContentManagerAPI日志dklog . log显示，调用RM检索文档花费了2.9秒的时间。
The DB2 Content Manager API log, dklog.log, shows that calls to RM to retrieve document is taking 2.9 seconds.
清单6显示ioctl调用导致用来格式化分区的mkfs程序失败。
Listing 6 shows that the ioctl call caused the MKFS program that was used to format a partition to fail.
查阅清单3中突出显示的调用sendImage 的代码。
See the highlighted code in Listing 3 for the call to sendImage.
下面的调用显示了如何对关系型DAS实现这一点。
The call below shows how this is done for the Relational DAS.
清单11中显示了如何调用脚本。
应用推荐