JBPM工作流补丁生成
我一直在我的项目中使用 JBPM 工作流程，并且有一个关于生成数据库补丁或 SQL 语句以应用 JBPM 工作流程修改的小问题。
目前，JBPM 工作流提供了一种通过部署最新流程定义来刷新模式中的 JBPM 表的方法。 但是，如果我的系统已经使用状态 X 部署的流程定义，并且现在我已修改流程定义文件以适应更改 X2，该怎么办？ 我仍然需要能够在不破坏旧保存数据实例的情况下部署增量更改。
是否可以仅为 JBPM 流程定义修改生成“增量”数据库脚本？ 还有哪些好工具可以用来更直观地修改流程定义？
重申一下我的问题，JBPM 部署会清理那里维护的旧实例的 JBPM 表，然后重新部署最新的文件； 如何在不删除旧数据的情况下生成增量？ 有没有任何用户友好的工具？
在这方面的任何帮助将不胜感激。
I have been using JBPM workflow in my project and I have a small question regarding generating the database patches or SQL statements to apply JBPM workflow modifications.
Currently JBPM workflow provides a way to refresh the JBPM tables in schema with the deployment of the latest process definitions. However what if my system is already live with process definition deployed with state X and now I have modified the process definition file to accommodate change X2. I still need to be able to deploy the delta changes without disrupting the instances of old saved data.
Is it possible to generate only "delta" database scripts for the JBPM process definition modification? And what are other good tools which can be used to modify process definitions more intuitively?
To reiterate on my problem, JBPM deploy cleans the JBPM tables of old instances maintained there and then redeploys the latest files; how do I generate the delta without deleting old data? Are there any user friendly tools for that?
Any help in this regard will be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不确定是否正确理解了您的问题。 当您部署新的流程定义时，JBpm 不会清理旧流程实例的表。
当您部署与现有流程定义同名的新流程定义时，您将获得该流程定义的新版本。
现有流程实例继续以其启动时的流程定义版本运行，而新流程实例则采用最新版本，除非您指定要使用的精确版本。
理论上，还可以修改流程定义以使用 API 运行流程实例。 这样做时，您必须注意使这些更改与这些实例的流动兼容。
I'm not sure to have understood correctly your issue. JBpm doesn't clean tables for old process instances when you deploy a new process definition.
When you deploy a new process definition with the same name of an existing one, you get new version of that process definition.
Existing process instances continue running with the process definition version they was started with, while new process instances take the latest version unless you specify the precise version to be used.
In theory, process definition can also be modified for running process instances using the API. In doing so, you must pay attention to make these changes compatible with the flowing of these instances.