[
https://jira.jboss.org/jira/browse/JBPM-2497?page=com.atlassian.jira.plug...
]
Joram Barrez resolved JBPM-2497.
--------------------------------
Resolution: Rejected
This is an unneeded feature: when a processInstance is deleted, the state of that
processInstance is stored in a HistoryProcessInstance, so no data is ever lost.
By doing so, the runtime table will remain small, while the history table will continue to
grow.
In jBPM3, a lot of uses complained that over time, the tables simply got too big. The
current mechanism fixes this problem.
So altough it would be easy to make this behaviour configurable, experience has shown us
that the current approach is the best approach for most users.
End always trigger deleteProcessInstance
----------------------------------------
Key: JBPM-2497
URL:
https://jira.jboss.org/jira/browse/JBPM-2497
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0
Reporter: Hauke Rabe
Why should the process instance immediately be deleted on end? At least this should be
configurable.
--
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