[jBPM Users] - Re: nested forks
by saraswati.santanu
We can use our understanding about the bug to have a hack for the time being.
We see task1 twice because the transition to task1 is the default transition of the fork node. To stop task1 from appearing twice we need to make sure that it is not the default transition. Instead we can add a dummy node for default transition to make sure that the rest of the forked nodes behave properly. We can try a flow like this:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <process name="ForumFlow2" xmlns="http://jbpm.org/4.0/jpdl">
|
| <start g="5,129,48,48" name="start1">
| <transition to="fork1"/>
| </start>
| <end g="957,121,48,48" name="end1"/>
|
| <task g="300,199,92,52" name="task2">
| <transition g="444,222:" to="join2"/>
| </task>
| <task g="334,329,92,52" name="task3">
| <transition g="679,358:" to="join1"/>
| </task>
| <task g="745,120,92,52" name="task8">
| <transition to="end1"/>
| </task>
| <task g="513,120,92,52" name="task9">
| <transition to="join1"/>
| </task>
| <task g="294,123,92,52" name="task1">
| <transition to="join2"/>
| </task>
| <fork g="211,130,48,48" name="fork2">
| <transition name="to java1" to="java1" g="235,68:-45,-18"/>
| <transition to="task1"/>
| <transition g="235,228:" to="task2"/>
| </fork>
| <join g="417,123,48,48" name="join2">
| <transition to="task9"/>
| </join>
| <join g="652,119,48,48" name="join1">
| <transition to="task8"/>
| </join>
| <fork g="93,126,48,48" name="fork1">
| <transition g="114,355:" to="task3"/>
| <transition to="fork2"/>
| </fork>
| <java name="java1"
| class="org.jbpm.test.DoNothingActivity"
| method="doNothing"
| g="301,41,92,52">
| </java>
| </process>
|
And a dummy java activity class
| package org.jbpm.test;
|
| /**
| * @author Santanu
| *
| */
| public class DoNothingActivity{
|
| public void doNothing() {
| System.out.println("Doing nothing");
| }
|
| }
|
This should give you correct list of tasks after the nested fork.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266409#4266409
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266409
16 years, 4 months
[jBPM Users] - Re: Problem moving from 4.1 to 4.2 using Spring configuratio
by RockerRocker
I am getting DBSession error due to this error --
| 16:14:51,625 INFO [STDOUT] Hibernate: select propertyim0_.KEY_ as KEY1_6_, propertyim0_.VERSION_ as VERSION2_6_, propertyim
| _.VALUE_ as VALUE3_6_ from JBPM4_PROPERTY propertyim0_ where propertyim0_.KEY_='next.dbid'
| 16:14:51,671 INFO [STDOUT] Hibernate: update JBPM4_PROPERTY set VERSION_=?, VALUE_=? where KEY_=? and VERSION_=?
| 16:14:51,734 INFO [DefaultCommandService] exception while executing command org.jbpm.pvm.internal.cmd.DeployCmd@1c0dc84
| org.hibernate.SessionException: Session is closed!
| at org.hibernate.impl.AbstractSessionImpl.errorIfClosed(AbstractSessionImpl.java:72)
| at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:558)
| at org.hibernate.impl.SessionImpl.save(SessionImpl.java:550)
| at org.hibernate.impl.SessionImpl.save(SessionImpl.java:546)
| at org.jbpm.pvm.internal.repository.RepositorySessionImpl.deploy(RepositorySessionImpl.java:60)
| at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:47)
| at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:33)
| at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
| at org.jbpm.pvm.internal.spring.CommandTransactionCallback.doInTransaction(CommandTransactionCallback.java:50)
| at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127)
| at org.jbpm.pvm.internal.tx.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:77)
| at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
| at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
| at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
| at org.jbpm.pvm.internal.repository.DeploymentImpl.deploy(DeploymentImpl.java:91)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266406#4266406
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266406
16 years, 4 months
[jBPM Users] - Re: nested forks
by makam
Thank you very much for your help, I have already reported the bug.
You think of any alternative for the management of the Fork? because I need to shoot 2 tasks,and one of the "optional", which is not controlled at the end. but without a Fork not how.
here ther is an example but not working
I would like the task 2 shot in Task 3 and Task 4, but I can not achieve.
| <process name="c" xmlns="http://jbpm.org/4.0/jpdl">
| <start g="15,176,48,48" name="start1">
| <transition to="task1"/>
| </start>
| <end g="655,182,48,48" name="end1"/>
| <task g="241,173,92,52" name="task2">
| <transition to="task4"/>
| <transition to="task3"/>
| </task>
| <task g="357,61,92,52" name="task3">
| <transition to="task5"/>
| </task>
| <task g="362,327,92,52" name="task4">
| <transition to="task5"/>
| </task>
| <task g="113,174,92,52" name="task1">
| <transition to="task2"/>
| </task>
| <task name="task5" g="489,181,92,52">
| <transition to="end1"/>
| </task>
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266383#4266383
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266383
16 years, 4 months
[jBPM Users] - Re: Jbpm 4 setup on existing JBOSS server
by xalperte
Sorry, I think I did not explained myself well.
The console I'm talking about is a console my company has built by itself. It's entirely different from the jBPM console and its fully integrated with our product.
By the way, are you using any configuration management tool like maven? If so, it can be very easy to create a JavaEE project (EAR) and test if that works.
My suggestion...
In order to do a "fast" test, you can create a maven j2ee simple project.
To do that you can run the following command:
maven archetype:generate
>From the list of archetypes you can select the option maven-archetype-j2ee-simple.
Only for test, you can add the jbpm4 dependencies to the pom.xml file of the "primary-source" module, and create a custom EventListener (src/main/java/....). You must create also a "test-process.bar" to call the event listener.
The last step will be add the "gwt-console" dependencies to the pom.xml file of the"ear" module. I do not know how many dependencies you will need, maybe inspect the jbpm4 maven repository could help you.
After that you can generate the ear file and deploy it to the jboss deploy folder in order to test if everything runs well.
Well, I don't know if exists a more easily way to test that.
I hope that will help you!.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266381#4266381
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266381
16 years, 4 months