Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion
"JBPM-2820 and JBPM-2702"
To view the discussion, visit: http://community.jboss.org/message/546001#546001
--------------------------------------------------------------
Hi HuiSheng,
please take a look at createExecution method in ExecutionImpl to verify if your fix is appropriate:
childExecution.save();
// make sure that child execution are saved before added to a persistent collection
// cause of the 'assigned' id strategy, adding the childExecution to the persistent collection
// before the dbid is assigned will result in identifier of an instance of ExecutionImpl altered from 0 to x
addExecution(childExecution);
// composeIds uses the parent so the childExecution has to be added before the ids are composed
childExecution.composeIds();
After your fix composeIds will be called twice, my concern is if that will not cause us any troubles. It is better to double check it.
Cheers
Maciej
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546001#546001]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
Toshiya Kobayashi [http://community.jboss.org/people/tkobayas%40redhat.com] replied to the discussion
"jBPM timer not executing/firing"
To view the discussion, visit: http://community.jboss.org/message/545999#545999
--------------------------------------------------------------
[main] DEBUG JobExecutor : starting thread group 'null'...
The message is not important. 'null' is just the name of JobExecutor.
First, I think you don't have to configure your own jbpm.cfg.xml.
jbpm-jpdl.jar:org/jbpm/default.jbpm.cfg.xml has properly configured JobExecutor and will be looked up if you don't have your own jbpm.cfg.xml.
Second, your problem is that your java process ends before JobExecutor captures timer jobs. Try Thread.sleep(10000) at the end of your main method.
This ad-hoc impl is ok if you just want to see how Timer works. But in real use case, you need to make sure the JobExecutorThread is alive. That's why the jbpm distribution contains job executor launcher servlet which run on an application server.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/545999#545999]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
Tej jbpm [http://community.jboss.org/people/tejJBPM] created the discussion
"JBPM Scalability and support"
To view the discussion, visit: http://community.jboss.org/message/545995#545995
--------------------------------------------------------------
Hi
We are using JBPM workflow engine for one of our big client. They have now raised question about the JBPM's scalability in handling huge volumes of processes. Has anybody tried in this line? Is it suitable?
Also I know it is under open source, but if needed is that possible to buy commercial paid support if we have any issues with the engine and it needs fixing?
Is there any chance they will withdraw JBPM as a open source? What happens then? ( I know i am thinking extreme..but we have to convince the client) do we have any document in JBPM website which highlights this?
Thanks very much for all your answers.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/545995#545995]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
Jaber C. Mourad [http://community.jboss.org/people/newbeewan] replied to the discussion
"JBpm 4 taskform integration in JSF"
To view the discussion, visit: http://community.jboss.org/message/545985#545985
--------------------------------------------------------------
> Maciej Swiderski a écrit:
>
> jBPM by default provides freemarker templates to display task forms, but it is mainly targeted to be used with BPM Console.
>
I'm using for now the form attribute to define jsf outcomes, it is not optimal, but as I'm not using bpm console it doesn't matter !
I need to define that outcome in faces-config to make it works, but that does the trick !
Regards
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/545985#545985]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]