The problem here is that the order of elements in the schema must not change from one conversion to another.
这里的问题是模式中的元素顺序在转换成另一个模式时不一定改变。
For those cases where you cannot change the schema, JAXB provides another solution.
对于那些无法更改架构的情况，JAXB提供了另一种解决方案。
You could change the default schema here if you used separate schemas for testing and deployment.
如果您要使用单独的测试和部署方案，那么您可以在这里改变默认的方案。
But we also keep looking on other methods and possibly will change or implement a new schema in next versions of our product.
但是，我们仍在寻找其他办法，在产品的下一个版本来改变或者实现一个新的方案。
You can choose either to change the schema, or disable the JAX-RPC data binding and integrate alternate data binding technologies.
您要么可以选择改变这个模式，要么禁止JAX - RPC数据绑定和整合候补数据绑定技术。
You can choose either to change the schema, or disable the JAX-RPC data binding and integrate alternate data binding technologies.
您要么可以选择改变这个模式，要么禁止JAX-RPC数据绑定和整合候补数据绑定技术。
And if the code version causing the schema change is in any way deficient, the change must often be rolled back by hand.
如果造成模式变化的代码版本仍然处在不完善的状态，那么经常必须手工回退变化。
Any change to an existing schema is managed there and must be properly approved before being deployed to a production runtime system.
现有模式的任何改变都得到管理并且在部署到生产运行时系统之前必须得到适当的许可。
Based on that taxonomy, we overview the impact of each change on schema validation.
按照这种分类，说明每种变化对模式验证的影响。
As a developer, I have no need to update or change a schema, much less deploy one!
作为开发人员，我无须更新或更改架构，更谈不上部署架构了！
The schema cannot change and the database cannot move without changes to all applications.
在没有改变的情况下，模式不能改变且数据库不能移植到所有的应用程序中。
Note that I'm not implying that you can't change a schema; I'm just saying that change is more easily accommodated without one.
注意，我并非暗示不能更改架构；我只是说，可以更轻松地适应变化。
It's not very likely that you can change the message schema of their service requests and ask them to put in a DOCTYPE statement.
您不太可能改变他们服务需求的消息模式，并让他们放入doctype语句。
You've taken a deep dive into a single migration but still haven't created a single change in the schema.
现在已经深入研究了单一迁移，但是还没有在模式中进行变化。
Figure 2: By associating actions to high level groups, you can add "team-specific" subgroups to the action without making a schema change.
图2：通过同高级别的群体联合行动，您能够将“团队特定的”子群体添加到行动中，而且不需要对计划做出改变。
For some XML configuration files, there is no XSL file because there is no schema change for them between versions 2.0.1 and 2.5.
对有些XML配置文件，没有XSL文件，因为2.0.1和2.5版本之间没有模式变化。
You could argue that a database schema doesn't change very often, but the fact is that it can and does change.
你可能争辩说数据库的Schema不会经常改变，但事实却恰恰相反。
To resolve the errors, change the location of the schema Department.xsd.
要解决这些错误，请更改架构Department . xsd的位置。
If you need to change a name after you have started work on your schema, make sure that everyone is aware of that change.
在您开始处理一个方案之后，您需要更改一个名字，那么您要确定每个人都意识到了您所做的更改。
This upgrade does not require any change in application code or the database schema.
这种升级不需要在应用程序代码或数据库模式方面做任何更改。
It meant that every time your service data structures changed the schema would also change, and clients would need to regenerate their code using the new schema.
它意味着，每次你的服务数据结构的改变都会引起模式的改变，客户端将需要使用新的模式重新生成它们的代码。
The first time that you cannot answer the question "In which version of which development schema was change X made?"
当您首次不能回答问题“更改x是在开发方案的哪一个版本之中完成的呢？”
Each team member can now easily assess which parts of their application would get impacted by a proposed schema change by the DBA.
现在，每个团队成员能够轻松地评估他们的应用程序的哪些部分将受到DBA提出的模式更改的影响。
This requires no change to the relational schema since the XML document is stored in a single column.
这将不需要对关系模式进行任何更改，因为XML文档存储在单个列中。
This command can only be used in cases where the change to the schema is backward-compatible, and the updated schema is automatically applied to all XML documents that are stored in the database.
只有以下情况才能使用该命令：模式的改变是向后兼容的；已更新模式被自动应用到所有存储在数据库的XML文档。
Similarly a database refactoring is a simple change to a database schema which improves the design without breaking nor adding anything.
类似的，数据库重构是对数据库方案的简单变更，是在不破坏且不添加东西的情况下改进设计。
Even if it is tempting to make a minor change on the Integration schema, the impact on future exports and imports is unforeseeable.
就算您试着对集成方案做一个小小的改动，对未来导入与导出的影响仍然是不可预测的。
Your displays need to change to reflect the changed authorization schema, and should now look like Table 6.
您需要对显示进行更改以反映更改的授权模式，更改后的显示应如表6中所示。
Schema definitions change, servers and networks go down, passwords expire, and so on.
模式定义变更、服务器和网络故障，以及密码过期等事件随时可能发生。
Another pitfall is that a change in the schema causes changes to the generated classes, which in turn has a knock-on effect to any code you've written around them.
另一个缺陷是如果修改方案，会造成生成的类也要修改，所以也就会对围绕它们编写的代码带来相应的影响。
应用推荐