GWTEventService 1.2.1 is released

[Sven Strohschein]

GWTEventService 1.2.1 is now released (to prevent doomsday... ;-) ) and will be published to the Central Maven Repository within the next hours.

GWTEventService 1.2.1 is a maintenance release which contains some optimizations and bug fixes. Some concurrency issues got fixed, which could occur in very rare situations. There is also a new property "eventservice.events.max" to limit the amount of events which are processed and transferred within one connection (cycle). This property is only important for applications which trigger a high amount of events per second (more than one hundred). The default value of 1.000 should be sufficient for the most applications.

GWTEventService 1.2.1 – Changelog (http://gwteventservice.googlecode.com/svn/branches/1.2.1/release-notes.html)

The maximum amount of events which is processed at once (within one call/request) can now be configured/limited and is set to 1.000 by default. Property: "eventservice.events.max"

Configuration dependent factories optimized and introduced lazy-loading

Various optimizations and fixes for the configuration loading mechanizm

Issue 33: The waiting user threads were not terminated directly when the user were removed by an unlisten call.

Issue 42: Client-side concurrency problem fixed which could occur when a listener gets added while received events are concurrently processed.

Issue49: The daemon thread to detect user/client timeouts is now stopped automatically when the EventService-Servlet gets deregistered.

Issue 52: The waiting user threads were not terminated directly on server shutdown (when the JVM were not terminated).

Issue 55: Concurrency problem fixed which could occur when GWTEventService is deployed on GlassFish.

(Tests revised with JUnit 4 and Mockito)