Essentially, retaining obliviousness is a matter of using the right type of annotation in the right situations, as discussed in the earlier guidelines.
事实上，保持遗忘性就是在正确的地方使用正确的注释类型，如在前面准则中所讨论的那样。
Each annotation type defines a fixed set of names associated with that annotation.
每个注释类型定义了一组与之关联的固定名称。
With the annotator aspect approach, the participation occurs only at the level of a Shared understanding of annotation type.
请使用注释者方面方法，参与只发生在对注释类型的共同理解这一级别。
Instead it adds an annotation to the field which informs the visual editor that the underlying type of this collection is String.
相反，它是为字段增加了注释，向可视化编辑器说明这一集合的隐藏类型为字符串。
Thus, when a type parameter t is used as the superclass of a generic class, the annotation on t tells us exactly what super-constructors we can call.
因此，当类型参数t用作泛型类的超类时，T的注释确切地告知我们可以调用哪些超级构造函数。
However, you'll find that several of your annotations might all use the same annotation type.
不过，您将发现多个注释都可能使用相同的注释类型。
The type is the actual construct used, and the annotation itself is the specific usage of that type, in a particular context (see the sidebar, Annotation or annotation type?).
类型是实际使用的结构，在特定上下文中，注释本身是该类型的具体使用（请参阅侧栏 注释或注释类型？）
This requires you to supply some sort of metadata on your annotation type, so that the compiler can enforce the annotation's intended functionality.
这就要求您为注释类型提供某种元数据，以便编译器保证按照预期的目的使用注释。
The selected annotation type specifies which result you are interested in, and the selected features of this annotation type specify the detailed part of interest.
选择的注释类型指定您感兴趣的结果，而该注释类型中选择的特征指定感兴趣的细节部分。
First, the derived aspect has a choice of annotation type.
首先，派生的方面可以选择注释类型。
An annotation is a particular type of feature structure that is attached to a region of the artifact being analyzed.
注释是一种特殊的特征结构，它被附加到需要分析的工件的某个区域。
You can prime JUnit to expect this failure by setting the expected value on the @Test annotation of the class type you expect to be thrown.
通过将您希望抛出异常的类类型的 @Test注释的值设置为 expected，可以使 JUit 提前预测到这种错误。
The @Pointcut annotation allows us to define pointcut expressions and, where necessary, the number and type of arguments to be bound by the pointcut.
@Pointcut注解允许我们定义切入点表达式，而且必要时，还有被切入点绑定的参数的个数和类型。
Because only a single bit of data is supplied, you can use a shortcut syntax (assuming the annotation type is defined to accept this syntax): @SingleValueAnnotation("my data").
因为仅提供很少的一点数据，所以可以使用快捷语法（假设注释类型接受此语法）： @SingleValueAnnotation("mydata") 。
This helps you ensure that nobody else takes your annotation type and misapplies it (or, better yet, that you don't misapply it in a fit of fatigue).
这样有助于避免他人误用您的注释类型(或者最好的地方是，您自己也不会因为疲惫而误用它)。
Produces annotation identifies a specific method as a producer method which is called whenever another bean in the system needs an injected object of the specified type.
Produces注解会将某个方法标识为生产方法，这样同一个系统下的另一个Bean如果需要该类型的对象就会调用这个生产方法。
Simple rules require changes to the regular expression, the annotation id to be created (unique for each rule), and the type of the annotation to be created.
简单的规则需要修改正则表达式、要创建的注释id(对于每个规则是惟一的)和要创建的注释的类型。
Note that some countries are detected in the first rule and an annotation of type "com.ibm.es.uima.Country" is created.
注意，第一个规则检测一些国家并创建一个“com . ibm . es . uima . Country”类型的注释。
The XML Forms Generator detects the need for an open selection through the use of a custom ECore annotation on an element or attribute that has an enumerated type.
XMLFormsGenerator通过在具有枚举类型的元素或属性上使用定制的ECore注释，检测对于open选择的需要。
Note that this annotation type doesn't have a single-member variable, so you gain nothing by naming one of the variables value.
因为该注释类型的成员变量不是一个，所以将一个变量命名为value没有任何意义。
Notice that Listing 13 specifies the annotation's retention as RUNTIME. This is a required aspect of using the Documented annotation type.
注意，清单13 中规定注释的保持性（retention）是RUNTIME ，这是使用 Documented 注释类型所必需的。
Further more, the id of the annotation to be created is changed to "thinkpad" with a type of com.ibm.es.uima.Thinkpad.
另外，将要创建的注释id修改为“thinkpad”，类型为com . ibm . es . uima . thinkpad。
You can define a named query as an annotation and execute it somewhere else in the code. Here is an example of using executing this type of named query.
您可以将命名查询定义为注释，并在代码中的其他位置执行它。
In these examples I'll focus on selecting join points by annotation type; further down I'll explain some of the other factors that can weigh in on join point selection.
在这些例子中，我将重点放在通过注释类型选择连接点上，然后我将进一步解释在选择连接点时，其他会起作用的因素。
When a pattern matches a part of the text, an annotation is created for the associated type.
当一个模式与文本的一部分匹配时，为相关类型创建一个注解。
You don't get the benefit of the shorthand syntax shown in Listing 5, so you might as well be a little more verbose and create better self-documentation for your annotation type.
因为不可能从清单5所示的简写形式中获益，所以您需要创建虽然稍微有点冗长，但是更容易理解的注释类型。
The annotation types used in the new rules must exist as part of the UIMA type system.
新规则中使用的注释类型必须成为uima类型系统的一部分。
The most obvious meta-annotation is one that allows you to indicate which program elements can have annotations of the defined type.
最明显的元注释就是允许何种程序元素具有定义的注释类型。
You can define the type of component inside template, or you can create an instance variable for the component and use the component annotation to define the component type and parameters.
你可以在模板中定义组件类型，或者你可以使用组件标注去定义组件类型和参数为组件产生一个实例变量。
The same applies to aspectual interfaces: You wouldn't want an annotation type called ReadLock whose purpose was to describe the use of the type.
对于方面化的接口也是一样：您可能不想使用名为ReadLock的注释类型，这类注释的用途是描述类型的使用。
应用推荐