December 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2575) event-listener propagation attribute not in jpdl-4.0.xsd

by Scott Peterson (JIRA)

event-listener propagation attribute not in jpdl-4.0.xsd -------------------------------------------------------- Key: JBPM-2575 URL: https://jira.jboss.org/jira/browse/JBPM-2575 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Reporter: Scott Peterson The user's guide shows how to configure an event-listener to receive propagated events. In jBPM 4.1, the following XML results in a SAX parse exception because the "propagation" attribute is missing from the xsd: <on event="start" > <event-listener class="com.principal.ris.jbpmDemo.events.StartEventListener" propagation="enabled"/> </on> -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-2709) Ant installer fails on start.eclipse with osx (mac) eclipse install

by Eric D. Schabell (JIRA)

Ant installer fails on start.eclipse with osx (mac) eclipse install ------------------------------------------------------------------- Key: JBPM-2709 URL: https://jira.jboss.org/jira/browse/JBPM-2709 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Environment: osX 10.4.11, intel x86, macbook Reporter: Eric D. Schabell Priority: Minor Fix For: jBPM 4.x Attachments: build.xml.diff In jbpm-4.3/install, 'ant start.eclipse' fails with message: Buildfile: build.xml [echo] database......... hsqldb [echo] tx............... standalone [echo] mail.smtp.host... localhost start.eclipse: [exec] -data: line 1: ../../jbpm-4.3/eclipse/eclipse: No such file or directory [exec] Result: 127 BUILD SUCCESSFUL Total time: 1 second Seems like you have two options: 1) provide a symlink to the correct location: ln -s PATH_TO_INSTALL/jbpm-4.3/ecipse/Eclipse.app/Contents/MacOS/eclipse PATH_TO_INSTALL/jbpm-4.3/eclipse/eclipse 2) start eclipse using correct path: ../../jbpm-4.3/ecipse/Eclipse.app/Contents/MacOS/eclipse I prefer the second so you need to update the jbpm-4.3/install/build.xml script as follows: --- build.xml 2009-12-28 11:10:36.000000000 +0100 +++ fixed-build.xml 2009-12-30 15:31:20.000000000 +0100 @@ -759,7 +759,7 @@ </fileset> </chmod> <exec executable="/bin/bash" os="Linux,Mac OS X"> - <arg line="-c "${jbpm.home}/eclipse/eclipse" "-data" "${jbpm.home}/workspace"" /> + <arg line="-c "${jbpm.home}/eclipse/jbpm-4.3/ecipse/Eclipse.app/Contents/MacOS/eclipse" "-data" "${jbpm.home}/workspace"" /> </exec> </target> Will attach this diff file for you. -- 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-2679) ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() silently fails if processinstance is not found

by Peter Horvath (JIRA)

ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() silently fails if processinstance is not found -------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2679 URL: https://jira.jboss.org/jira/browse/JBPM-2679 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Environment: JBPM 4.2 Reporter: Peter Horvath ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() should throw an exception if the specified process instance is not found. Current ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() implementations call the method public void deleteProcessInstance(String processInstanceId, boolean deleteHistory) in DbSessionImpl The code tries to lookup the process instance, but the deletion is only attempted if the process instance is found: ExecutionImpl processInstance = (ExecutionImpl) findProcessInstanceByIdIgnoreSuspended(processInstanceId); if (processInstance!=null) { // delete remaining tasks for this process instance List<TaskImpl> tasks = findTasks(processInstanceId); for (TaskImpl task: tasks) { session.delete(task); } // delete remaining jobs for this process instance JobImpl currentJob = EnvironmentImpl.getFromCurrent(JobImpl.class, false); List<JobImpl> jobs = findJobs(processInstanceId); for (JobImpl job: jobs) { if (job!=currentJob){ session.delete(job); } } if (log.isDebugEnabled()) { log.debug("deleting process instance "+processInstanceId); } session.delete(processInstance); } Since not finding a process instance usually indicates an error, the method should throw an exception to notify caller code. I think this code should be modified to throw an exception if the process instance is not found: ExecutionImpl processInstance = (ExecutionImpl) findProcessInstanceByIdIgnoreSuspended(processInstanceId); if (processInstance==null) { throw new JbpmException("processInstance is not found"); } ... -- 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-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] 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2009