October 2008 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: jbpm3: signalling tokens through the jsf console

by kukeltje

Yep, one of the lesser used features. Certainly skipping for this release. In the future if the taskinstances related to a token are taken into account it becomes more interesting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185049#4185049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185049

17 years

1
0
0 / 0

timer tests

by Tom Baeyens

Hi Alejandro, you removed the exclusions that i introduced <exclude>org/jbpm/scheduler/exe/TimerDbTest.java</exclude> <exclude>org/jbpm/taskmgmt/exe/TaskTimerExecutionDbTest.java</exclude> now this fails on my machine. For some reason, these problems do not show up in the hudson matrix. Does anyone else see those tests fail in the current trunk ? -- regards, tom.

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task lifecycle in jbpm3

by tom.baeyens＠jboss.com

yes. suspending and resuming tasks individually can be considered non sense. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185040#4185040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185040

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: build failing ?

by tom.baeyens＠jboss.com

i got those process archive tests working now also on jdk 6. the problem was that i checked if the ProcessClassLoader found a certain class by loading the class in a process archive, then removing the class from the file system (cause there it is in the test classpath) and then deploying the archive and then using the class. the 2 tests were somehow interfering. i don't know the cause. but it turned out that the test classloader already loaded the action handler before the test began. so the even though the actionhandler was loaded with the process classloader, it was already found previously by the parent of the process classloader before. ps. kukeltje, are you already back awake ? well... in case your were, i'm sure that after reading the previous explanation you have been put back to sleep for another couple of days :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185038#4185038 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185038

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: jbpm3: signalling tokens through the jsf console

by tom.baeyens＠jboss.com

You are right. We might expose the signal as an admin operation. But that should not have priority. Can be skipped. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185035#4185035 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185035

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task lifecycle in jbpm3

by heiko.braun＠jboss.com

So, that means it's nonsense in the current console, right? Then I'll drop it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185028#4185028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185028

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Task lifecycle in jbpm3

by tom.baeyens＠jboss.com

Suspending a process instance means that the tasks won't show up in task lists and that timers don't get executed. I don't think that suspend/resume should be offered on the task or token level, but only on the process instance. Starting is optional. In jBPM 4, the lifecycle of a task is configurable with a process. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185009#4185009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185009

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Analytical and operational dashboards

by KrisVerlaenen

At this point, I believe the database itself could almost be considered an API, it defines the data that could be reasoned on. Currently there is need to put a Java API on top of that, as it will become very difficult to create one that is both generic enough to support all use cases and specific enough to offer simple methods to end users. I do believe though that it could be useful to define a "minimal" schema (the minimal data that the db should contain to make it useful), and think about making that extensible so people can add more information later (and be able to use that extra information somehow in the analysis). Are there any plans to support business indicators (KPIs)? Because people usually don't really reason about "the number of process instances", more about "outstanding orders", "the time to complete an order", etc. This might be somewhat related to CEP: creating higher-level business events from lower-level process events. Just a thought for the future though, to support business users. Simple operational dashboards for admins are probably the first step towards that. Heiko: I'd love to hear about your ideas / technology / progress on this next week, you don't be surprised if I ask you that question ;) Kris View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184984#4184984 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184984

17 years

1
0
0 / 0

[Design of JBoss jBPM] - jbpm3: signalling tokens through the jsf console

by heiko.braun＠jboss.com

Currently it's possible to signal a token through the console, but it doesn't respect the task instances that might be associated with a process instance. IMO the only interaction with a process instance from the console should be through tasks and direct signalling be forbidden. What's the use case behind this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184952#4184952 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184952

17 years

1
0
0 / 0

[Design of JBoss jBPM] - Task lifecycle in jbpm3

by heiko.braun＠jboss.com

Of hat use is the task lifecycle in jbpm3? Looking at the jsf console reveils start,suspend, resume and end. Every task is associated with a form. When it get's submitted the task is completed. So to me, lifecycle of incomplete, complete would make sense, but I don't understand the meaning of 'suspending' a task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184950#4184950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184950

17 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev October 2008