您可以看到它具有特定的格式。
您可以看到它十分简单。
这里，您可以看到它的卫星照片。
这实际上是一个强大的概念，并且您可以看到它提供的可能性。
This really is a powerful concept, and you can see the possibilities it has to offer.
您可以看到它正在进行IP接管，并随后启动WebSphereMQ进程。
You can see that it is doing the IP takeover and then starting WebSphere MQ processes.
它比原来的代码好多了，因为您可以看到它正在做什么，可从重用部分获益。
"It's much better than the original code because you can see what it's doing, allowing harvesting of the reusable parts."
在Binding选项卡中，您可以看到它指向您先前部署的服务实现的端点地址。
In the Binding TAB, you can see that it points to the endpoint address of the service implementation that you deployed earlier.
这同我们在上一小节创建的扩展的结果是一样的，在图2中您可以看到它的屏幕截图，如前所述。
The result of this is identical to that of the extension we created in the previous section, and you can see a screen shot of it in action in Figure 2, as seen earlier in this article.
如果您选择使用memcached作为缓存解决方案，那么我敢保证您可以看到它的效率如何。
If you choose to leverage memcached as your caching solution, I am sure you will see just how effective it is.
当您打开该项目时，您可以看到它包含三个目录：publish、rules和src，如图2所示。
When you open the project, you see that it contains three directories: publish, rules, and SRC, as shown in Figure 2.
如上面的清单3所示，您可以看到它包含对于该序列和两个AcknowledgementRange元素的标识符。
As shown in Listing 3 above, you see that it includes the identifier for the sequence and two AcknowledgementRange elements.
您可以看到，这是一个非常简单的过程，但是它已经足够进行任何种类的静态分析。
As you can see, this is a very simple process, but it is more than sufficient for performing any sort of static analysis.
您可以在图10中看到它。
您可以在实现文件中看到有一个标记，它包含一个 标记。
You can see in the implementation file that there is a tag which contains a tag.
在接口文件中，您可以看到有一个标记，它包含一个标记和一个表示我已经选择的端口的标记。
In the interface file you can see that there is a tag which contains an and also a tag which represents the port I have already chosen.
同样，您可以看到一个对象引用另一个对象(它仅包含我正在查找的对象的一个向量)的编程方式的模式。
Again, you can see the programmatic pattern of one object referencing another object that simply contains a vector of the object (s) I am really looking for.
正如您可以看到的，WSIF的API由以WSDL编写的抽象服务描述驱动；它完全从实际使用的绑定中分离出来。
As you can see, WSIF's API is driven by the abstract service description in WSDL; it is completely divorced from the actual binding used.
然后，您可以看到目标WSDL并且存储它。
You can then see what the target WSDL looks like and save it.
在打开它时，您可以看到此参与的人工任务的详细属性，如图50 所示
When you open it, you can see the detailed properties for this participating human task, as Figure 50 shows
您可以看到，它包含的是嵌入的LTPA 令牌，而不是原始的Username 令牌。
You can see that it contains the embedded LTPA token, instead of the original Username token..
例如，您可以看到详细窗口有一个名为Diagram的选项卡，它包含一个Name字段，其值为MyProcessDiagram。
For example, you can see that the details window has a TAB named Diagram, which contains a name field whose value is MyProcessDiagram.
您可以在样例文件 e4xstockEnv.wsdd 中看到它。
SQS 采用 “最终一致性（eventual consistency）”模型，这意味着您可以向队列发送消息，但是队列的消费者不一定能够在特定的时间段内看到它。
SQS follows the model of "eventual consistency," meaning you can send a message to the queue, but a consumer of that queue may not see the message for some significant period of time.
您可以看到交付过程的描述和该过程的其他详细信息，例如它属于哪个配置。
You can see the description of the delivery process and other detailed information about the process, such as the configurations to which it belongs.
如果您未看到异常或装入模块错误，那么您可以假定它成功了。
If you see no exception or load module errors, you can assume it succeeded.
您可以把它四处移动，但是无论它在哪里，您都应该能看到您输入的请求。
You can move it around, but wherever it is, you should see the request that you just entered.
您可以看到使用此机制如何使您能够影响ESB的行为，以及它如何基于您存储在注册中心的策略定义对传入请求进行处理。
You can see how using this mechanism enables you to influence the behavior of the ESB, and how it handles incoming requests based on policy definitions you store in the registry.
正如您可以看到的，这段代码非常复杂，它创建了一些代码来遍历XML文档，从而检索所需要的信息。
As you can see, it's relatively complicated to create the code that walks the XML document to retrieve the information that you need.
如果搜索结果页面是公共的，则您可以直接看到它。
不过，如果您可以将惯用模式从其他代码中凸显出来，这样就可以更容易地看到它的不同。
However, if you can make the idiomatic pattern stand out from other code, it's easier to see that it is in fact something different.
应用推荐