-
1. Re: where is the class org.jbpm.pvm.internal.cfg.SpringConfiguration in 4.4?
rebody Jul 21, 2010 8:29 PM (in response to zhangjing2000)Hi Jing,
There are lots of changes for spring intergration in jBPM-4.3. Please refer developer guide for the newest way to intergrate spring.
http://docs.jboss.com/jbpm/v4/devguide/html_single/#springIntegration
And here is a chinese translation version:
http://www.family168.com/tutorial/jbpm4devguide/html/springIntegration.html
-
2. Re: where is the class org.jbpm.pvm.internal.cfg.SpringConfiguration in 4.4?
zhangjing2000 Jul 22, 2010 9:50 PM (in response to rebody)Huisheng,
Thanks to your reply. Now my code can run on jbpm 4.4, but I run into a new issue -- no history data are stored in jbpm history tables. I don't have these issues in jbpm 4.2. Is there any new change on history event support in jbpm 4.4? I checked dev guide, could not find any clue.
I attached the jbpm.cfg.xml. Wonder if need some changes in this file.
Thanks ahead,
-
jbpm.cfg.xml 2.3 KB
-
-
3. Re: where is the class org.jbpm.pvm.internal.cfg.SpringConfiguration in 4.4?
rebody Jul 22, 2010 11:02 PM (in response to zhangjing2000)Hi Jing,
First, we recommand using the default configuration files which included in distribution files. If you really want to use your own configuration files, please compare them carefully.
Since jBPM-4.3, we could use history session chain to add our own history listener, and the default configuration like this:
<history-sessions> <object class="org.jbpm.pvm.internal.history.HistorySessionImpl"/> </history-sessions>
Please refer developer guide for more information: http://docs.jboss.com/jbpm/v4/devguide/html_single/#d0e1420
-
4. Re: where is the class org.jbpm.pvm.internal.cfg.SpringConfiguration in 4.4?
zhangjing2000 Jul 23, 2010 7:28 PM (in response to rebody)Thanks Huisheng,
I have solved the issue. The reason we did not use default jbpm cfg file is because the spring support in jbpm4.2 is not very smoothy, we load every element into a single configuration file so can easily do troubleshooting. We will consider to use the default jbpm cfg file in future. Thanks to your advise