Hide Forgot
Date of First Response: 2008-12-01 01:01:31 project_key: SOA Platform issue for JBESB-2163
Link: Added: This issue depends JBESB-2163
More information needed for release note: "We need to change it to use the expected methods" For explaining to the end-user, why are these the expected methods?
Hiya Darrin. Each gateway/listener is supposed to follow a standard lifecycle, where the gateway/listener is informed of state changes through invocations on event methods (initialise, start, stop, destroy) and is expected to carry out specific tasks in response. Some of these methods (start/stop) are also exposed through MBeans and provide an administrator with the ability to suspend/resume processing if they should choose to. The ScheduleListener, on the other hand, had provided a separate mechanism that was neither controlled by the lifecycle controller nor exposed through the MBeans. The fix for this issue involved changing the ScheduleListener behaviour so that it adhered to the standard lifecycle and could, therefore, be controlled and exposed in the same manner as the other gateways/listeners.
Release Note: ScheduleListener now adheres to the standard gateway/listener lifecyle mechanism
Verified present in 4.2 CP03