there are reasons why i don't want to make the first node 'async'. so i kept
looking for a way to signal a process asynchronously. this is what i
implemented:
a AsyncProcessSignalJob that can be saved as a jbpm-job. then the job executor
finds and executes the job as any other job.
|
yeah, if i had started from scratch i would have taken the path with the
'async' node.
but that was not an option (already deployed processes with long running
process instance; want to keep new versions to an absolute minimum) in my case.
also, i remember another posting in this forum where
i know about the 'async' attribute. but it does not what i want.
what i need is a possibility to start the process asynchronously.
using 'async' in a node whould mean to start the process synchronously and then
continue asynchronously when the first node is executed.
any other suggestions?
Hello,
i want to start a new process instance in an asynchronous way.
what i think of is a solution where i create a process instance and then call a
| processInstance.signalAsync();
|
The call to signalAsync() does return immetiately and the process instance is
scheduled like a timer
hello,
is there a tool that produces java source code from a process definition and
generates string constants for node-names, transition-names and so on?
like from
|
| process-definition xmlns= name=my-process
|
| start-state name=start-state
| transition
simple question: does the gwt-console run on tomcat?
or is jboss required?
king regards,
hans
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4210012#4210012
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4210012
thank you for this information.
leads to another question related to log retrieval:
is there a tool out there that displays the process history (ie. path token has
taken) for a process instance? i can't find such thing in jbpm-console (3.2.3).
i know it would not be hard to code that but would
does the gwt-console run under tomcat 5.5?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4207823#4207823
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4207823
___
jboss-user
thank you for your answer.
a more detailed question:
what if i have 1.000.000 timers (jobs) with 10.000 jobs due each day? can the
jobexecutor handle that? is there a notable performance impact when it queries
the jobs-table?
hans
View the original post :
yeah, i tried it with preprocessing the duedate and storing it in a process
variable. wasn't happy with this solution though.
current solution: i replaced JbpmVariableResolver with my own class which
extends from it and implemented a quick hack that allows to call method of
spring beans.
for
hello,
i would like to dynamically calculate the due date of timers at runtime.
| timer duedate=#{myBean.calcDueDate} name=timer1
|
a few questions:
* whats the correct syntax for method binding?
* besides SEAM are there other expression evaluator implementations that
hi,
rodrigorev wrote : rodosa, i have try your code in the jbpm-console and work!.
|
| the timer repeat each 10 seconds but in my webapp deployed in tomcat still
doesn't work.
|
|
is JobExecutorServlet configured in your webapp?
View the original post :
hi,
i want to update an already deployed process definition with minor changes (add
new transition, change duedate of timers) without creating a new version of the
process definition.
what is the easiest way of updating a process definition?
do i have to create a new version and then move
hello,
has anybody experience with the maximum number of process instances and jobs
that jbpm can handle reasonably?
can it handle 100.000 or 1.000.000 running process instances?
any information is highly appreciated.
thank you,
oliver
View the original post :
14 matches
Mail list logo
