如何从2.0.0.RC2 spring批量版本迁移到2.0.4?
我必须将我的项目从 2.0.0.RC2 版本迁移到 2.0.4。但问题是 2.0.4 的 xsd 与 2.0.0.RC2 不同。这意味着我的工作配置都不起作用。
2.0.0 RC2 中的作业配置是
<batch:job id="taskletComponentTestJob">
<batch:step id="taskletTestComponent"
tasklet="taskletForTestComponent">
<batch:listeners>
<batch:listener ref="customStepExecutionListener" />
</batch:listeners>
</batch:step>
<batch:listeners>
<batch:listener ref="customJobExecutionListener" />
</batch:listeners>
</batch:job>
2.0.4 中的作业配置将是
<batch:job id="taskletComponentTestJob1">
<batch:step id="taskletTestComponent" >
<batch:tasklet ref="taskletForTestComponent">
</batch:tasklet>
</batch:step>
<batch:listeners>
<batch:listener ref="customJobExecutionListener" />
</batch:listeners>
</batch:job>
是否有任何实用程序可以使我现有的所有作业配置与 2.0.4 兼容? 另外,更改配置后我还会遇到任何进一步的问题吗?
I have to migrate my project from 2.0.0.RC2 version to 2.0.4. But the problem is the xsd of 2.0.4 is different then 2.0.0.RC2. That means none of my job configuration is going to work.
Job configuration in 2.0.0 RC2 was
<batch:job id="taskletComponentTestJob">
<batch:step id="taskletTestComponent"
tasklet="taskletForTestComponent">
<batch:listeners>
<batch:listener ref="customStepExecutionListener" />
</batch:listeners>
</batch:step>
<batch:listeners>
<batch:listener ref="customJobExecutionListener" />
</batch:listeners>
</batch:job>
Job configuration in 2.0.4 will be
<batch:job id="taskletComponentTestJob1">
<batch:step id="taskletTestComponent" >
<batch:tasklet ref="taskletForTestComponent">
</batch:tasklet>
</batch:step>
<batch:listeners>
<batch:listener ref="customJobExecutionListener" />
</batch:listeners>
</batch:job>
Is there any utility by which all my existing job configuration will become compatible to 2.0.4?
Also, after changing the configuration will i face any further problem ?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我对此表示怀疑。但是,如果您有大量需要转换的文件,您可能可以编写一些 Perl 脚本或 XSLT 脚本来自动执行该任务。
很有可能,是的。
令我惊讶的是,Spring Batch 开发人员在开发周期的后期才更改了架构。而且你有权感到有些恼怒......我认为。但是,当您基于“发布候选版本”开发代码时,您会面临这样的风险。
I doubt it. But if you have a large number of these files that need to be converted, you could probably write a little Perl script, or XSLT script to automate the task.
Quite possibly, yes.
It does surprise me that the Spring Batch developers changed the schema so late in the development cycle. And you are entitled to be somewhat miffed ... IMO. But that's a risk you take when you develop code based on an "Release Candidate".