Bug 100482

Summary: event processors need access to the session's flushAll() method
Product: [Retired] Red Hat Web Application Framework Reporter: Vadim Nasardinov <vnasardinov>
Component: persistenceAssignee: Archit Shah <archit.shah>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-09-24 20:07:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 98546, 100484    

Description Vadim Nasardinov 2003-07-22 20:26:16 UTC
While the com.redhat.persistence.Session class and its flushAll()
method are both public, there is no sanctioned way to get the
session object that I am aware of.  This is by design.

However, the versioning event processor needs to be able to
call ssn.flushAll().  This is needed in order to correctly
support the methods suspendVersioning() and resumeVersioning().

suspendVersioning() must flush all pending events before turning
versioning off.

Likewise, resumeVersioning() must flush all pending events before
turning versioning back on.

Comment 1 Vadim Nasardinov 2003-07-24 14:34:12 UTC
I see that the flushAll() method was added to com.redhat.persistence.Session 
in changelist 33910. 
 
The question remains, how do I get the session object?  
SessionManager.getSession() returns com.arsdigita.persistence.Session -- 
not com.redhat.persistence.Session. 
 
 

Comment 2 Vadim Nasardinov 2003-07-24 14:50:56 UTC
never mind

this can be closed