Bug 100482 - event processors need access to the session's flushAll() method
Summary: event processors need access to the session's flushAll() method
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: persistence
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Archit Shah
QA Contact: Jon Orris
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 98546 100484
TreeView+ depends on / blocked
 
Reported: 2003-07-22 20:26 UTC by Vadim Nasardinov
Modified: 2007-04-18 16:55 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2003-09-24 20:07:12 UTC


Attachments (Terms of Use)

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



Note You need to log in before you can comment on or make changes to this bug.