Sure, the component got the wrong resource and therefore didn't work right, but thanks to caching, it failed really fast.
当然，组建取得了错误的资源当然不能正常工作，但是，要感谢缓存，它失败的却是很快。
Just as predicted, overloaded resource names and a caching service locator makes the code execute differently; it makes some components get the wrong resources.
正如所预测的那样，重载的资源名和缓存服务定位器使得代码执行有不同的结果，它使某些组件取得错误的资源。
It will deploy successfully and seem to run correctly, but will run into subtle and difficult-to-diagnose problems when a component USES the wrong resource.
这些程序可能部署成功并且表面上看起来运行正确，但当组件使用了错误的资源时将引起微妙的并且难以诊断的问题。
Some opt to transition one running instance from one physical resource over to another should something go wrong; others simply transition the IP addresses from one instance to another.
某些提供商选择在发生错误时会将正在运行的实例从一个物理资源转至另一个物理资源；其他一些提供商则直接将IP地址从一个实例转至另一个实例。
The first version of the JCA specification provided a mechanism for a resource adapter to indicate to the connection manager when something has gone badly wrong with a connection.
JCA规范的第一个版本提供了一种让资源适配器在连接出现严重错误时通知连接管理器的机制。
There's nothing wrong with giving away a free resource in exchange for someone's email address.
赠送免费资源交换某人的邮件地址是无可厚非了。
Anytime you ask developers to manage resource life cycles, you will face the bugs that come about when that management goes wrong.
只要让开发人员管理资源的生命周期，就少不了因管理出错而引起的Bug。
I have a website that is a completely free resource with over five hundred articles on a wide range of subject matter, so you can't really go wrong here!
我有一个网站，是拥有五百多篇文章，主题涉及面广泛的完全免费的信息资源，在这里你不会真的误入岐途。
I have a website that is a completely free resource with over five hundred articles on a wide range of subject matter, so you can't really go wrong here!
我有一个网站，是拥有五百多篇文章，主题涉及面广泛的完全免费的信息资源，在这里你不会真的误入岐途。
应用推荐