[
http://jira.jboss.com/jira/browse/JBPM-392?page=all ]
Tom Baeyens closed JBPM-392.
----------------------------
Fix Version/s: (was: jBPM jPDL 3.2.1)
Resolution: Won't Fix
this issue won't be fixed as a jbpm API.
the problem is that the logs refer to the task instance data, even when the process is
ended. so the historic information would have to be removed in order for the task data
to be removed. in the next generation version of jbpm, we'll be starting with a real
business intelligence solution that duplicates all the information in the historic
archive.
instead, users will have the following workaround: they can do for now: use hibernate
bulk delete to remove the logs that have references to the task instances (similar for
any other type of runtime data). then, use the bulk delete to remove the task instances
themselves.
cancel taskInstances, messages and timers when process instance ends
--------------------------------------------------------------------
Key: JBPM-392
URL:
http://jira.jboss.com/jira/browse/JBPM-392
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
when a process instance ends, we should have an option to remove or cancel all open
taskInstance, messages and timers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira