1.In fact, avoiding this style of coupling was one of the motivating factors behind the creation of Enterprise JavaBeans (EJB) technology.
实际上，避免这类耦合是创建企业JavaBean（EJB）技术背后的一个动机。
2.If the box were unchecked, then the template would be inactive, so it would not be offered as an option in the Insert JavaBeans wizard.
如果复选框没有选中，那么模板就是未激活的，这样它就不会作为InsertJavaBeans向导中的选项提供。
3.As you can see, JavaBeans-style properties are reduced down to straight name accessors, as if they were fields.
您可以看到，JavaBeans样式的属性被简化为使用名称直接访问，这就好像它们是字段一样。
4.JSP custom tags and JavaBeans make it possible for you to separate the user interface and workflow logic.
JSP定制标签和JavaBeans使得将用户界面和业务逻辑分离成为可能。
5.These services can be implemented as remote Enterprise JavaBeans (EJB) method calls, web services, or CORBA calls, just to name only a few.
这些服务可以作为远程企业JavaBean（EJB）方法调用、Web服务或CORBA调用（这里只列出几个）来执行。
6.There is nothing in the JavaBeans specification that requires you to create anonymous inner classes for event listening.
在JavaBeans规范中，没有要求您创建匿名内部类进行事件监听。
7.As you can see below, the controller specifies three JavaBeans properties that will be used to collect input and display results.
正如从下面可以看到的，控制器指定三个JavaBeans属性，这些属性将用于收集输入和显示结果。
8.These JavaBeans will implement the operations necessary to carry out the use-cases identified in this document.
这些JavaBean将实现完成这篇文档中确定的用例所必需的各种操作。
9.I'll demonstrate a variety of methods you can use to turn your JavaBeans into XML documents, and you'll learn the pros and cons of each.
我将演示可以把JavaBeans变成XML文档的各种方法，并且讨论每种方法的优劣。
10.Notice that the lack of a no-argument constructor violates the JavaBeans standard, which insists on a default constructor.
需要注意的一点是，无参数构造函数的缺失违反了JavaBeans的标准，该标准坚持要有一个默认的构造函数。