January 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2708) TimerImpl prints out signalname rather than event name when a timer event is fired and hence the signalname is null

by Martin Porter (JIRA)

TimerImpl prints out signalname rather than event name when a timer event is fired and hence the signalname is null ------------------------------------------------------------------------------------------------------------------- Key: JBPM-2708 URL: https://jira.jboss.org/jira/browse/JBPM-2708 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: Eclipse 3.5, Vista, Oracle 11g, Reporter: Martin Porter Priority: Minor The TimerImpl class prints incorrect diagnostic message when a timer event is fired as it prints the signal name and not the event name. As per the lines in the code below:- if (eventName!=null) { ObservableElement eventSource = execution.getActivity(); if (log.isDebugEnabled()) log.debug("firing event "+signalName+" into "+eventSource); execution.fire(eventName, eventSource); } signalName should read 'eventName' instead. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPM-1883) Provide an initial implementation of a AS4 deployer

by Thomas Diesler (JIRA)

Provide an initial implementation of a AS4 deployer --------------------------------------------------- Key: JBPM-1883 URL: https://jira.jboss.org/jira/browse/JBPM-1883 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.3.1 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
4
0 / 0

[JBoss JIRA] Created: (JBPM-2701) add ejb invoke testability of the java activity

by Tom Baeyens (JIRA)

add ejb invoke testability of the java activity ----------------------------------------------- Key: JBPM-2701 URL: https://jira.jboss.org/jira/browse/JBPM-2701 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Koen Aers Fix For: jBPM 4.4 -- 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
1
0 / 0

[JBoss JIRA] Assigned: (JBPM-1209) support for expressions

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1209?page=com.atlassian.jira.plug... ] Tom Baeyens reassigned JBPM-1209: --------------------------------- Assignee: Tom Baeyens > support for expressions > ----------------------- > > Key: JBPM-1209 > URL: https://jira.jboss.org/jira/browse/JBPM-1209 > Project: jBPM > Issue Type: Feature Request > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 4.4 > > > this issue incorporates 2 aspects: > * review all attributes in jpdl where expression resolving is appropriate. validate with a test. > * in the java activity, add the capability to refer to the target object with an expression. that way, the java activity can be used to invoke methods on process variables. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBPM-2659) Add DB2 to QA axis

by Joram Barrez (JIRA)

Add DB2 to QA axis ------------------ Key: JBPM-2659 URL: https://jira.jboss.org/jira/browse/JBPM-2659 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Alejandro Guizar Priority: Minor Fix For: jBPM 4.3 -- 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
2
0 / 0

[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-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-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-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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2010