Code style vs. annotations and XML.
代码风格与注释和XML的比较。
Complete annotations of data source models.
完成数据源模型的注释。
Full annotations have multiple data members.
完整注释有多个数据成员。
Again, the interesting code is in the annotations.
同样，这里的注释代码也很有趣。
On the whole, I'd rather write my own annotations.
总的来说，我更愿意自己编写注释。
Notice there are no JPA annotations on this field.
请注意该字段没有jpa注释。
Create the POJO with the appropriate annotations.
创建具有适当注解的POJO。
The selectedCourse property now has two annotations.
selectedCourse属性现在有两个注释。
What if you want to interpret your own annotations?
如果你想要解释自己的注解该怎么办呢？
The annotations in Listing 7 should look familiar.
清单7 中的注解应该看起来很熟悉。
First, program elements must carry metadata annotations.
首先，程序元素必须包含元数据注释。
Picture of the thing being described, with annotations.
被描述事物的图片，带注解。
Part 2 in this article series will explore custom annotations.
本系列文章的第2部分将研究定制注释。
For example, here are annotations for a function's parameters.
例如，如下所示的是针对某函数的参数的注释。
Further annotations in the same package define advice methods.
在同一个包中更多的注解定义了通知方法。
Enables automatic scan for the class that has Spring annotations.
启用对带有Spring注释的类进行自动扫描。
One of the most important new features is support for annotations.
最为重要的一个新特性是支持注释。
The final form of the specific annotations may change in future drafts.
特殊注解的最终形式在未来的规范草案中可以有所改动。
It also contains the annotations that are created during the analysis run.
它还包含在分析运行期间创建的注释。
You can define annotations for toString generation in many different ways.
可以以多种方式为toString的生成定义注释。
All of the code written so far is just back-end code plus some annotations.
至此我们所写的所有代码都是一些后端代码和注释。
However, supplying annotations in a crosscutting manner can be very helpful.
不过，以横切的方式提供注释是很有用的。
The same trend will probably occur with annotations, albeit to a lesser degree.
注释也可能出现同样的趋势，虽然不一定到那种程度。
The only parts of it that might seem unfamiliar at first are the annotations.
其唯一可能初看起来不熟悉的部分是注解。
This is simply the text that was marked for the annotations in the text analyzer.
这正是在文本分析器中为注释标记的文本。
Despite the benefits of annotations, I see two main drawbacks to their (over) use.
在注释的优势之外，我看到了它们过度使用的两个主要不足。
But are annotations always the best way to provide configuration-type information?
但是难道注释总是提供配置类型信息的最佳方式吗？
For example, they must have their own target namespace and must have annotations.
例如，它们必须具有自己的目标名称空间，并且必须具有注解。
Over time, the knowledge base for a given source is enriched by these annotations.
随着时间的推移，针对一个给定源的知识库会增加这些标注。
Single-value annotations are similar to markers, but provide a single piece of data.
单一值注释与标记注释类似，但提供一段数据。
应用推荐