| 1. | Unmarshal method and the full sequence for the
解编排方法的完整抽象操作序列。 |
| 2. | From part 1 refactored to use the abstract operation monitor as a base aspect
，它使用抽象操作监视器作为一个基本方面。 |
| 3. | Represents a named set of abstract operations and the corresponding abstract messages
表示命名的抽象操作集和相应的抽象消息。 |
| 4. | A port type is a named set of the abstract operations and messages involved
端口类型就是命名了的一组抽象操作和涉及到的消息集合。 |
| 5. | Listing 5 shows bytecode generated from the list of abstract operations shown in listing 4
清单5显示了清单4中的抽象操作列表产生的字节码。 |
| 6. | Method should generate information such as operation binding , abstract operation , and messages
方法的实现应生成操作绑定、抽象操作和消息等信息。 |
| 7. | The general idea of abstracting operations to simplify data management is valid , no matter how you implement it
不管如何去实现，抽象操作以简化数据管理的总体想法是正确的。 |
| 8. | The abstract operation monitor also provides pointcuts with concrete advice that define common ways to monitor requests
在抽象操作监视器中，还提供了具有具体建议的切点，它定义了监视请求的常用方法。 |
| 9. | Listing 6 shows java source code generated from the same list of abstract operations as used for the listing 5 bytecode
清单6显示了抽象操作列表生成的java源代码，这组抽象操作与生成清单5中字节码的抽象操作相同。 |
| 10. | Listing 4 gives a list of abstract operations required to implement unmarshalling from xml to java objects for the bottom left portion of the figure 2 diagram
清单4为图2的左下部分给出了实现从xml到java对象的解编排所需的抽象操作列表。 |
