If there is no component alias, no implicit authentication will occur.
如果没有组件别名，则不会出现隐式身份验证。
No component matching is required and all passive element feature a low sensitivity.
不需要元件匹配，所有无源器件的灵敏度都非常低。
No component was damaged and input fuse shall not blow when LED driver is powered on.
开机瞬间任何零件以及保险丝不得烧毁。
No component matching is required and the sensitivities are low all of the passive parts.
不需要元件匹配，所有无源器件的灵敏度都非常低。
The service requester and the mediation flow component itself did not change at all, hence no programming was involved.
服务请求者和中介流组件本身根本不会发生改变，因此不涉及到编程工作。
Each component should be given only the authority it needs to do its own job and no more.
每个组件仅应该得到完成它本身工作所需的权限，不多不少。
In this article, you identified the game as the most important component of your infrastructure — without it, customers have no reason to come to your enterprise.
在本文中，我们讨论了游戏基础结构中最重要的组件——游戏。如果没有游戏，用户就不会访问您的站点。
Similarly, no change is required to accept changes to those values from other component views.
同样，从其他组件视图接受这些值的更改时，不需要进行任何更改。
We now have an SCA component with an interface, but no implementation.
现在，我们的SCA组件具有接口，但没有实现。
The result is almost a kind of magic — by following a few simple rules, a J2EE application can automatically gain transactional semantics with little or no additional component code.
结果简直是一种魔术—通过遵守几条简单的规则，J2EE应用程序就可以自动获得事务性语义，只需极少或根本不需要额外的组件代码。
Timeouts are less of a concern in those cases, because there is no dependency in an upstream component on the timeliness of processing requests downstream.
在此类情况下，超时不是重要考虑事项，因为上游组件对于处理请求下游的时限并无依赖。
No need to include testing code inside the component code which can be time consuming and lead to the unexpected introduction of software defects.
无需在组件代码内包含测试代码，因为这很耗时且容易引发意外的软件问题。
A wide variety of tasks can be performed prior to performing a forward, but no response headers can be set by the forwarding component and no content can be sent to the output buffer.
在转发之前可以执行很多类型的任务，但是要转发的组件不能设置响应头部信息，也不能有内容发送到输出缓冲区。
Reality: The risk associated with having one developer per feature or component is that no one else can maintain and understand that feature.
事实：一个部分只用一名开发人员完成有很大的风险：没有第二个人可以维护和理解这个部分的内容。
Every SCA runtime provides the SCA binding, also known as the default binding, meaning that it's the binding used when no other binding is specified for a component reference or service.
每个SCA运行时都提供了SCA绑定，即所说的缺省绑定，也就是用于未为组件引用或服务指定其他绑定的情况。
However, there's no one aspect that can be used to definitively state the granularity of a component.
不过，任何单个方面都不能用来明确地确定组件的粒度。
If you just feel like removing a component and installing a better one, it is no big deal.
如果只是想删除组件并安装更好的组件，也很简单。
The current focus owner is the component that has received a FOCUS_GAINED but no FOCUS_LOST event (see below for more on these events).
当前的焦点所有者是个已收到FOCUS_GAINED事件—但还未收到FOCUS_LOST事件的组件(有关这些事件的更多信息，请参阅下面的内容)。
Fig7 means there is no formula defined for this component, which is determined by its parent and siblings.
fig7表示这个组件没有公式，它由其父节点和同胞节点决定。
While devised strictly for the purpose of demonstration, my cloud-to-mobile app contains no traditional view component and largely models itself off of existing, successful services.
虽然为了演示，对Magnus进行了严格的设计，我的云到移动终端的应用程序不包含传统的视图组件，主要包含了现有的成功服务的模型。
Clients of these services won't be aware of the difference, but in the implementation, an EJB component will be no different than a regular CDI bean with EJB stereotypes applied.
这些服务的客户端将感觉不到任何差异，对于实现来说，EJB组件与常规的CDIBean(使用了EJB模型)也没有什么不同。
It is simple to construct a reference to a Classic SCA component since no special configuration is needed.
构造对ClassicSCA组件的引用非常简单，因为不需要任何特殊配置。
There's an SCA component passing some double values by reference to another SCA component, so no data transformations or protocol translations have to take place.
一个SCA组件通过参照另一个SCA组件传递一些double值。因此没有出现数据转换或协议转换。
This one has no y component and this one has no y component, so this is very easy.
它没有y轴分量,它没有y轴分量，这非常简单。
Unlike the example in Listing 1, with declarative transaction demarcation there is no transaction management code in the component methods.
与清单1中的示例不同，由于有宣告式事务划分，这段组件代码中没有事务管理代码。
You must ensure there are no unacceptable dependencies of one service component for other components and remove all redundancies.
您必须要确保一个服务组件对其他组件不存在不可接受的依赖项并删除所有依赖项。
Currently there is no way for a component controller to process part of an event and then propagate it up to a higher controller for further processing.
当前尚没有一种方法可以做到让某个组件控制器处理部分事件，然后再将其传播到更高层的控制器做进一步的处理。
If a component (or service) has no potential for reuse, then it should probably not be deployed as a service.
如果组件(或服务)不可能重用，就不无法将其作为服务进行部署。
Since a mediation flow is treated like any other component now, there is no longer a need for a specialized mediation module.
由于现在将中介流与任何其他组件一样对待，因此不再需要专门的中介模块。
Since a mediation flow is treated like any other component now, there is no longer a need for a specialized mediation module.
由于现在将中介流与任何其他组件一样对待，因此不再需要专门的中介模块。
应用推荐