November 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2172) integrate jboss identity component

by Tom Baeyens (JIRA)

integrate jboss identity component ---------------------------------- Key: JBPM-2172 URL: https://jira.jboss.org/jira/browse/JBPM-2172 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Jeff Yu Fix For: jBPM 4.0.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
20
0 / 0

[JBoss JIRA] Created: (JBPM-2536) Make Job retry logic configurable

by Peter Horvath (JIRA)

Make Job retry logic configurable ---------------------------------- Key: JBPM-2536 URL: https://jira.jboss.org/jira/browse/JBPM-2536 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Peter Horvath Currently retry count is hard-coded to JobImpl (org.jbpm.pvm.internal.job.JobImpl.retries) This number should be configurable / there should be an option to completely disable job retries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2543) Enhance query API with operations needed for JOPR plugin

by Joram Barrez (JIRA)

Enhance query API with operations needed for JOPR plugin -------------------------------------------------------- Key: JBPM-2543 URL: https://jira.jboss.org/jira/browse/JBPM-2543 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0, jBPM 4.1 Reporter: Joram Barrez Assignee: Joram Barrez Priority: Minor Fix For: jBPM 4.3 The following operations where demanded by Jim Ma for his JOPR plugin work (and I agree that they are needed). 1. JobQuery : query by job id 2. query historyTasks by process definition id" . 3. The api to query the average process instance duration . I get this value by sum and divide the process duration . It will be faster if there is the same api as the get average activity duration. 4. The api to get the process deployment , process definition , process instances , task number . It can be retrieved by calling the collection size . It will be efficient to select count(*) from database . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2416) introduce task audit capabilities

by Tom Baeyens (JIRA)

introduce task audit capabilities --------------------------------- Key: JBPM-2416 URL: https://jira.jboss.org/jira/browse/JBPM-2416 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 task history and all history in general should be configurable in a declarative manner. on a task definition, a process or in the process-engine context, it should get a boolean audit attribute. if audit for a task is enabled, all variable updates for that will be recorded. for now, it is sufficient if the audit attribute has potential values {enabled,disabled}. In the future, the value for the audit attribute could get more fine grained specification based on individual (commaseparated list of) use cases. it must be possible to combine audit with the isHistoryEnabled on the variable declaration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2329) re-introduce timers in the userguide

by Tom Baeyens (JIRA)

re-introduce timers in the userguide ------------------------------------ Key: JBPM-2329 URL: https://jira.jboss.org/jira/browse/JBPM-2329 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 change jpdpl schema of the timers: from <on event="timeout"> <timer duedate="10 minutes"/> <event-listener class="org.jbpm.examples.timer.event.Escalate" /> </on> to <timer duedate="10 minutes" fire-event="timeout"> <event-listener class="org.jbpm.examples.timer.event.Escalate" /> </timer> and re-introduce the timers back in the userguide -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2485) Accessing the parent/super execution from a subprocess execution

by Flavio Donzé (JIRA)

Accessing the parent/super execution from a subprocess execution ---------------------------------------------------------------- Key: JBPM-2485 URL: https://jira.jboss.org/jira/browse/JBPM-2485 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Flavio Donzé See the forum reference for the description -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2652) Sanetize jBPM 3

by Tom Baeyens (JIRA)

Sanetize jBPM 3 --------------- Key: JBPM-2652 URL: https://jira.jboss.org/jira/browse/JBPM-2652 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.4, jBPM 3.2.9 https://docspace.corp.redhat.com/clearspace/docs/DOC-29094 i've associated this to jbpm 4.4 just for planning purposes. so that i'll take it into account for that release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1987) create optimistic locking test

by Tom Baeyens (JIRA)

create optimistic locking test ------------------------------ Key: JBPM-1987 URL: https://jira.jboss.org/jira/browse/JBPM-1987 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.Beta1 create a test that produces an optimistic locking failure. this will 1) verify that the db isolation works correctly 2) allow us to see how this gets logged. (in jbpm 3, a lot of people complained because there were still SOSEs in the logs) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-2117) get schema reviewed by real dba

by Tom Baeyens (JIRA)

get schema reviewed by real dba ------------------------------- Key: JBPM-2117 URL: https://jira.jboss.org/jira/browse/JBPM-2117 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0.CR1 gert leenders might know someone that might be willing to have a look at it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
14
0 / 0

[JBoss JIRA] Created: (JBPM-2624) ERROR org.hibernate.hql.PARSER in InitializePropertiesCmd.java

by Michael Wohlfart (JIRA)

ERROR org.hibernate.hql.PARSER in InitializePropertiesCmd.java --------------------------------------------------------------- Key: JBPM-2624 URL: https://jira.jboss.org/jira/browse/JBPM-2624 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Environment: Ubuntu 9.04 Oracle JDBC Driver version - "11.1.0.6.0-Production+" Java(TM) SE Runtime Environment (build 1.6.0_14-b08) Oracle Database 10g Express Edition Release 10.2.0.1.0 jBPM 4.3-SNAPSHOT Reporter: Michael Wohlfart Priority: Trivial the query for maxDbid in InitializePropertiesCmd.java gives me a ERROR org.hibernate.hql.PARSER - line 1:12: unexpected token: object I think this is caused my the "as" keyword not supported in oracle. the following change in InitializePropertiesCmd.java fixed this for me: for (String persistedType: persistedTypes) { try { Long maxDbid = (Long) session.createQuery( - "select max(object.dbid) " + - "from "+persistedType+" as object" + "select max(dbid) " + + "from "+persistedType ).uniqueResult(); if ( (maxDbid!=null) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2009