Let's make it clear:
1) Signalling is when the task (s) are done the (last one, the first one, etc.
Look for signal attribute in task-node) task that is ended signal the token to
continue the execution. If you don't check this option (or put the attribute)
when you end some task you need to
Hi thanks for your help with answering the second question, it is reassuring to
hear that this could be an explanation...
Regarding my first question.. I assume I should have both the 'blocking' and
'signalling' check boxes checked for each task in the processes ?
Thanks again,
Ross
View the
Hi,
I am just in the process of rolling out a new version of one of our processes,
to test the blocking versus no blocking update impact, and indeed to see
whether this will fix our problem.
In the Eclipse properties tab for a given task, I assume I should have both
blocking and signalling
Yes, of course it's posible, that's your problem
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4187431#4187431
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4187431
___
jboss-user
And that's the difference between the blocking and non blocking tasks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4187434#4187434
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4187434
Hi,
I have looked through the latest process to exhibit this problem, and examined
the tasks in the eclipse properties panel.
The 'Signalling' checkbox is ticked, and the 'Blocking' checkbox is not ticked.
So Salaboy21's post may shed some light on this for me.
Can anyone confirm it is
Hi,
reading the snippet again, which Salaboy21 posted in an earlier post, I must
confess to having difficulty grasping the difference between signalling and
blocking tasks...
| Task instances can be signalling. A signalling task instance is a task
instance that, when completed, can send a
You are right,
anonymous wrote :
| It looks like both types of task halt execution until task completion
|
The diference is that a blocking task need that the tasks created inside this
node must be ended to continue. This means that you can not signal a task node
to continue the execution
Hi,
I will go through the process and ensure the tasks are 'blocking'.
What I am keen to do, is gain the ability to recreate this multi-state
behavior.
We are using a modified version of the demo JSF webapp to allow users to work
through several different processes. So transitioning is
Hi,
I will try to piece together a concise report on some implementation details,
to attach to a post on Monday,
thanks for your help,
Ross
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4186179#4186179
Reply to the post :
Better yet, make a unit test with embedded processdefinition and needed
actionhandlers (as embedded classes) that demonstrates the problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4186187#4186187
Reply to the post :
Hi guys,
back again on this topic... unfortunately this is still a problem with our
implementation, and before we roll this marvellous engine out to other
projects, of course the boss is expecting me to solve this problem.
I imagine the problem is related to how we have implemented and
Yes, like said kukeltje before, you must look about the properties of your
tasks.
Signaling and Blocking properties are important in multiuser environments.
Let us know the details of your implementation.
View the original post :
Hi,
clutching at straws here, could it be transaction related? I cannot remember
if transactions are enabled by default?
Regards,
Ross
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149302#4149302
Reply to the post :
anonymous wrote : A user will submit his or her task, and instead of just
flowing to the next task, in sequence, several are then created and listed as
not started.
|
Just for clarification, I take it that the several task instances that are
created, are all from different nodes, at not all
Hi dleerob,
thanks for trying to help.
Examining process instance 787, there is one token listed against it : 920,
this in turn is linked to one node : 2863, (with a name_ of 'dm rejection
reason').
This is indeed the node which the process image states is currently running.
The problem is,
if you signal a token instead of ending a task (and have that signal the token)
you get unfinished tasks but tasks not related to a token anymore so
unexpected behaviour (like you have now)
just my 0.01 eurocents
View the original post :
This could be because your tasks are not blocking... Or i miss understand your
problem...
Look in this direction...
anonymous wrote : Task instances can be blocking, meaning that the related
token (=path of execution) is not allowed to leave the task-node before the
task instance is completed.
Hi,
all of our tasks are signalling, so when they are completed process execution
is continued. What is interesting here is that we are almost certain that the
task has not been 'submitted', yet a subsequent task has also been created and
is in the 'not started' state simultaneously.
Thanks
sorry, no, I have not seen any behaviour like this before.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149260#4149260
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4149260
___
20 matches
Mail list logo
