Bug #212 (closed)
EventHandler should store and re-insert Stateful Events.
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | minor | Cc: | |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
Like ProxyCleanupFilter and SessionHandler, our AOP interceptors almost always need to check for instances of StatefulServiceInterface. In the case of EventHandler, the Event that is created on first use should probably be reattached to the Thread much like is done with the Session in SessionHandler.
Change History (7)
comment:1 Changed 18 years ago by jmoore
- Keywords changed from stateful, session, aop, interceptor to stateful, session, aop, interceptor, iteration5
- Milestone changed from Unscheduled to 3.0-M3
comment:2 Changed 18 years ago by jmoore
- Keywords changed from stateful, session, aop, interceptor, iteration5 to stateful, session, aop, interceptor, iteration6
comment:3 Changed 18 years ago by jmoore
- Keywords changed from stateful, session, aop, interceptor, iteration6 to stateful, session, aop, interceptor
- Milestone changed from 3.0-M3 to 3.0-M4
Infrastructure is in place. Need importer in trunk for testing. Rescheduling with Rendering cleanup (milestone:3.0-M4)
comment:4 Changed 18 years ago by jmoore
r1024 adds RenderingEngine.getCurrentEventContext() to check Events.
comment:5 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Duplicate of #326
comment:6 Changed 18 years ago by jmoore
- Keywords changed from stateful, session, aop, interceptor to stateful, session, aop, interceptor, iteration1
comment:7 Changed 17 years ago by jmoore
- Keywords changed from stateful, session, aop, interceptor, iteration1 to stateful, session, aop, interceptor
Rescheduling with #328