| Summary: | ScheduleListener ignores lifecycle events | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Kevin Conner <kevin.conner> |
| Component: | JBossESB | Assignee: | Kevin Conner <kevin.conner> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 CP02 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP03 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1021 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-13 11:58:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Kevin Conner
2008-11-14 17:37:01 UTC
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 |