Stateful EventContext is broken

[jmoore]

Currently only stateless sessions properly handle the loading, saving, and unloading of event context (Events, EventLogs, etc.). The stateful services should maintian this state themselves. For that, the SecuritySystem will have to be reworked.

[jmoore]

Depends on #328

[jmoore]

This is most likely the cause of any non-determinism seen in RenderingBean? and co. But to test it, I need the test fixture from the importer. Rescheduling for milestone:3.0-M4.

[jmoore]

r1024 adds RenderingEngine.getCurrentEventContext() to check Events. (Should probably be added to StatefulServiceInterface?)

[jmoore]

#212 marked as duplicate.

[jmoore]

r1025 implements the storing and reseting of EventContext instances for stateful services. There are several improvements to be made (refactoring, EventLog handling,...) but ornately weird behavior should stop.

r1026 provides a test in source:branches/bioformats-omero

[jmoore]

r1031 significantly fixes SessionHandler. Stateful and stateless services have separate proxy stacks (and separate abstract Spring beans). SessionHandler unit test is also again functional.

[jmoore]

r1034 fixes a NPE in SessionHandler unit test. Only thrown on particular orderings of methods. (Worse from command line)

[jmoore]

Closing this. I've seen no concrete issues over many iterations. I'll add a note to review this on wiki:proposals/SessionsAndMessages