代码本身没有改变，但是需要修改模块的元数据。
The code itself does not change, but the module metadata needs to.
还可以根据需要相对较快地改变技术，因为重要的设计信息是一个抽象模型，没有嵌入到代码中。
And you can change technologies reasonably quickly as needed because the important design information is in an abstract model, not embedded in the code.
在企业内部需要为IT系统控制代码的地方，可以考虑使用SOAP之外的服务调用方法，这些方法可能没有构建并解析XML内容。
Inside the enterprise, where you have control over the code for it systems, you can consider approaches other than SOAP for service invocation, possibly without building and interpreting XML content.
更明智的方法是，仅在需要多次使用代码，并且对于您希望实现的任务没有可用的内置php函数时才定义函数。
The wiser way is to define functions only when you need to use the code multiple times and there are no PHP built-ins for the task you want to achieve.
如果代码检测没有快速找到泄露，则您可能需要执行一些应用程序转储并分析它们以找到引用增加了的对象。
If code inspection does not quickly find the leak, you will probably need to take some application dumps and analyze them to find the objects whose references are growing in size.
下面的代码并没有先请求所有的记录，然后对所需要的记录进行分片，而是在实际的查询中使用了5作为OFFSET、10作为LIMIT，这可以极大地提高性能。
Rather than request all the records and then slice the records needed, the code below USES an OFFSET of 5 and a LIMIT of 10 in the actual SQL query, greatly improving performance.
首先，他承认对遗留环境(代码没有测试)采取高覆盖率的确需要长期的高投入。
First he concedes that getting high coverage in place for a legacy environment (one where the code does not have tests) does require a potentially high, long-term investment.
在方法开发项目中，没有必要编写和测试代码，但是仍然需要测试所有的连接。
There is no need to write and test code during a method development project, but there is still a need for testing all links and usage threads.
您只需要指定事务属性(没有回滚代码或回滚指令！)
You only need to specify the transaction attributes (no rollback code or rollback directives!)
当你部署应用时，你并不需要上传任何附加文件——没有任何多余到模板、工具或代码库。
When you come to deploy your applications there are absolutely no additional files - no extra templates, tools or code libraries - that you have to upload.
如果不知道该堆栈的一些元素的信息(例如因为“应用程序代码”还没有测试，或刚刚测试好)，您需要另一种方法。
If you do not know that information for some elements of the stack (e.g. because the "application code" has not been tested yet, or so far has tested fine), you need another approach.
您不需要帮助也能编写某个脚本或某段代码，然而，手头上却没有所需的数据或资源。
You don't need help writing a particular script or piece of code; rather, you need data or resources that you simply don't have.
示例源代码中有一个需要注意之处：此代码没有针对维护进行优化，只针对可读性进行了优化。
A word about the sample source code: the code is not optimized for maintenance, but for readability.
因为将此代码移植到Linux不需要修改，所以没有必要进一步分析。
Because no changes are needed to transplant the code to Linux, no further analysis is needed.
表1描述了没有Ajax的视图层，还指出了需要的代码假设控制器层由servlet实现，视图层由JSP技术实现。
Table 1 describes the MVC view layer without Ajax and indicates the amount of code needed, assuming that the controller layer is implemented by servlets and the view layer by JSP technology.
因为现在关于CometAPI还没有一个标准，还需要很多特定于容器的代码，社区的帮助会加快进度并提高稳定性。
Since there is no standard right now in terms of Comet API, a lot of container specific code will be required and the help of the community will probably speed up the release and stability.
如果没有对代码进行单元测试，那么在升级或支持新浏览器后，组织可能需要花钱反复测试Web应用程序。
Without unit testing this code, organizations may pay for repeated testing of web applications after upgrading or supporting new browsers.
因此，当asymmetricbinding在作用域中时，它和当前CXF代码一样坚持生成签名，即使没有什么需要签署。
So it looks like the current CXF code insists on generating a signature when an AsymmetricBinding is in scope, even when nothing is being signed.
不要害怕扔掉代码.重构和重新编码是两个非常重要的领域.当你遇到已经不存在的需求,或者你没有意识到你能找到比开始编写的代码更好地解决旧问题和新问题的方案,如果你遵循上面的建议,需要重构的代码已经最小化了.如果你没有遵循上面的建议,你可能需要重新编码.
Many developers solve their problem while they are coding, and there is nothing wrong doing that. As a matter of fact, you can do that and still adhere to the above statement.
在这个简化的代码中，我们没有对不同的错误进行特殊处理；不过，在实际的实现中，需要使用这些不同的路径。
In this simplified code, we have no special treatment of the different faults; however, in a real implementation, we would need to exercise these different paths.
对于这个示例，有更多的代码需要说明，但与第一个线程示例相比，它并没有复杂多少，这正是因为使用了队列模块。
This example has a bit more code to explain, but it isn't that much more complicated than the first threading example, thanks to the use of the queuing module.
如果没有JDBC，您需要编写特定于每个具体数据库的自定义代码。
Without JDBC, you would need to write custom code specific to each particular database.
显然，您需要那些方法才能执行代码，但是这里列出它们没有意义。
Obviously, you'll need those methods to get the code to execute, but there was no point listing them here.
同样，对于使用了EJB组件的代码没有做任何修改。如果您用本地接口代替了远程接口，那么客户端代码将需要进行相当大的修改。
Also, no changes are made to code that USES the EJB components; if you replace remote interfaces with local ones, then considerable change may be required for client code.
这段代码中没有错误处理功能，但要注意，实际应用程序需要此功能。
There's no error handling in this code, but note that you would need it in a real-world application.
至少我现在有一组要求代码必须能够通过的测试，到现在为止，我还没有进入需要大量返工的编码阶段。
At least I now have a set of tests the code must pass, and I haven't gotten so far into coding that the amount of rework is excessive.
如果希望在自己的应用程序中使用这些方法，那么并没有什么真正神秘和奇妙的东西需要添加到您的代码中。
If you want to use these methods in your own applications, there's really nothing weird and wonderful to add to your code.
关于覆盖报告您需要了解的主要事情是，覆盖报告最好用来检查哪些代码没有经过充分的测试。
The main thing to understand about coverage reports is that they're best used to expose code that hasn't been adequately tested.
请记住，这纯粹是出于教学目的也许有人会说我不想为产品代码编写测试，但我确实没有在编写产品代码，所以我不需要编写正式的测试。
Remember, folks, this is purely for pedagogical purposes fancy author-speak for "You really don't want to do this for production code, but because I'm not writing production code, I get to cheat."
请记住，这纯粹是出于教学目的也许有人会说我不想为产品代码编写测试，但我确实没有在编写产品代码，所以我不需要编写正式的测试。
Remember, folks, this is purely for pedagogical purposes fancy author-speak for "You really don't want to do this for production code, but because I'm not writing production code, I get to cheat."
应用推荐