[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4629) Disable default behaviour of auto-save for process instances
Tihomir Surdilovic (JIRA)
jira-events at lists.jboss.org
Wed Apr 7 08:36:42 EDT 2010
[ https://jira.jboss.org/jira/browse/JBSEAM-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tihomir Surdilovic updated JBSEAM-4629:
---------------------------------------
Fix Version/s: 2.2.1.CR2
> Disable default behaviour of auto-save for process instances
> ------------------------------------------------------------
>
> Key: JBSEAM-4629
> URL: https://jira.jboss.org/jira/browse/JBSEAM-4629
> Project: Seam
> Issue Type: Bug
> Affects Versions: 2.2.1.CR1
> Reporter: Tihomir Surdilovic
> Fix For: 2.2.1.CR2
>
>
> When injecting org.jboss.seam.bpm.ProcessInstance in a Seam components the code ends up in the following code snipped of this class:
> ********
> if (processId!=null)
> {
> //TODO: do we need to cache this??
> return ManagedJbpmContext.instance().getProcessInstanceForUpdate(processId);
> }
> ********
> the org.jbpm.JbpmContext#getProcessInstanceForUpdate(processId) method will get a process instance from the db and will register it for auto-save. It will then be saved automatically at the close() .
> Continuous registering for auto-save can cause performance issues as when the jbpmContext closes it will save all instances in the autoSaveProcessInstances list which can be huge.
> The proposed fix is to change to the code to:
> if (processId!=null)
> {
> return ManagedJbpmContext.instance().getProcessInstance(processId);
> }
--
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
More information about the seam-issues
mailing list