代码迁移只是答案的一部分。
开始进行代码迁移的第二步。
增量地进行代码迁移提供很多有价值的东西。
各个线程将其代码迁移到不同的运行服务器上。
Each of the threads migrates its code to a different run server.
有了应用程序的“正确”运行，代码迁移的最后阶段就是按需要优化代码。
With the application running "right," the final stage in code migration is to optimize the code as required.
事实上，代码迁移可能只是整个迁移过程的一小部分(对J2EE应用而言肯定是这样)。
In fact, code migration can be a small part of the overall migration process (this is certainly true for J2EE applications).
在最近的一个迁移工程中，我们跳过了确定作用域阶段，开发人员直接进入到代码迁移阶段。
On a recent migration project, the scoping session was skipped and our developers went right into the code migration phase.
这个奇特的现象经常发生在收购其它公司后，以及当代码迁移和重新培训开发团队的费用过高的时候。
This particular phenomenon usually occurred after acquisition of other companies and when the cost of migration and retraining of development teams was perceived as too great.
让我们来看一些php新的面向对象特性，并了解如何将现有PHP V 4代码迁移到PHP V5。
Take a tour through some of PHP's new object-oriented features and learn how to migrate existing PHP V4 code into V5.
jQuery 1.3发布版在性能上是很出色的，光凭这点，您就应该将代码迁移到这个版本。
The 1.3 release was a big release in terms of performance, and for this reason alone, you should move up to this release level in your own code.
提出的代码迁移策略具有更高的灵活性，代码构造算法及代码存储结构可以有效地支持代码传送。
The code migration strategy presented is more flexible than the others, the code conformation algorithm and the code storage structure efficiently support the code transmission.
通常，重组应是正常开发过程的一部分(事实上，在“代码迁移”阶段，一定数量的重组应是自然发生的)。
In general, refactoring should be part of the normal development process (in fact, some amount of refactoring should naturally occur during the "Code Migration" stage).
例如，这里提出的代码迁移阶段的“使它运行”这一步可能需要一些另一个应用服务器及它所提供的服务方面的知识。
The "get it running" step of the Code Migration stage presented here, for example, may require some knowledge of the other application server and the services it provides.
在完成代码迁移之后开始的“使它正确运行”这一步，需要具备把现有应用程序升级到J2EE所要求的技能。
The "get it running right" step, which starts after the code is migrated, depends on skills required to upgrade an existing application to J2EE.
也就是说，实际的代码迁移工作应该在开发人员接受 J2EE 1.3培训和开发环境改变后的几周之内立即开始。
That is, developers should get training in J2EE 1.4 and development environment changes no more than a few weeks before starting an actual code migration effort.
为实现那个目的，创造了用于发现代码迁移问题的自定义规则，这些规则为工具提供了解决许多此类问题的快速修复方案。
To that end, custom rules for discovering code migration problems were created and provide the tool with quick fixes for resolving many of these issues.
在这种情况下，将应用程序的源代码迁移到新编程模型并进行改写，以便您可以将迁移的应用程序部署到ProcessServer。
In this case, the source code for the application is migrated to the new programming model and reworked so that you can deploy a migrated application to Process Server.
如果您知道它是如何在该平台上运行的并且有测试案例的结果证明它，那么您就能够证明迁移后的代码是按预期运行的。
If you know how it works on that platform and you have results from test cases to prove it, you can prove that your migrated code functions as expected.
为应用程序代码确定迁移策略。
使迁移后的代码能运行并就让它那样就行了。
一般情况下，代码质量对迁移的复杂性不会有直接的影响。
In general, code quality does not have a direct impact on migration complexity.
通过代码检查，您可以估计出迁移的绝对大小。
Through a code review, you can gauge the absolute size of the migration.
确认迁移后的代码按预期的运行。
在迁移过程中，测试案例应随代码一起迁移。
While doing the migration, test cases should be migrated along with the code.
迁移不仅仅包括代码或单一的环境。
Migration involves more than just code or any single environment.
您必须手动迁移这些代码以使用SCA编程模型调用业务流程。
You must manually migrate this code to use the SCA programming model to invoke the business process.
在迁移现有代码之前，请确保它在另一个应用服务器上是按预期运行的。
Before you migrate existing code, make sure it works as expected in the other application server.
安装、配置和测试迁移后的应用程序代码。
您可以从初始代码开始遵循练习，一次迁移应用程序的一部分。
You can follow the exercise starting from the initial code and migrate the application one piece at a time.
这些会给测试部署大量复杂代码修改或者大型迁移的时候，带来难以想像的便捷性。
This allows for unbelievable flexibility when testing new deploys that have complex code changes and do large migrations.
应用推荐