[Design of JBoss jBPM] - Re: process patch files
by camunda
The process patch frigthens me a bit. Of course it is nice to just patch some small errors (like typos or RuntimeExceptions in Actions). But with good tests ou don't need that too much.
So the process patch application is really to find some business problems never thougth of before (like the example of Britt, I also have a bunch of examples for it). But there I like it more to deploy a new process definition and somehow move old processes to the new version.
And if this is implemented by a Command in the jbpm core, it is not really dirty or hacking. And if yoi provide a mapping of old process states to new process states it is nor fare away from you process-update file.
I see no need for other stuff, and as I like the idea of only having this way with new process version.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053238#4053238
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053238
18 years, 10 months
[Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss
by camunda
I would also appriciate a single wiki site where all the requirements are collected.
I want to add some comments to various points:
- process versioning: What I like in the current deployment model is the control you have, YOU decide when you deploy and if you include the classes or not. And that should not be somehow automated, at least in production.
- a version attribute in the xml and maybe a attribute if to include classes would be interessting option (much better than hash I think). Waiting for jbpm 3.3 should not be a showstopper for this.
- normally there are many different versions with running processes around. It is quite normal in long running business processes (like Britt said)
- I like the protability of jBPM very much. And I think it is a important advantage that should be kept. Today it runs in standalone, Tomcat, JBoss or other AS environments. Very important in my eyes. So some proprietary JBoss deployment should be always (or at least in the near future) additional. Thats what the people like about jBPM, it is not tied to some AS.
Bernd.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053225#4053225
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053225
18 years, 10 months