Fire Lifecycle callbacks respecting Ordered interface [SPR-3755]

[spring-projects-issues]

Ben Rowlands opened SPR-3755 and commented

Some active components (ie, those that are started/stopped) have strict Lifecycle ordering requirements with respect to other components.

For example, a JMS message listener container should be started after any components used by the listener are started (otherwise we may receive messages from the container before these dependent components are started).

For example client transports used by the service will need to be started before the server is started. The shutdown order should be reversed so the input to the server is shutdown before the client transports are stopped (so any in flight messages can be flushed out before shutdown).

The only way to achieve this at the moment is to introduce a custom lifecycle interface (and propagate start/stop manually). Ideally we'd use the Ordered mix-in interface with Lifecycle to provide richer control over inter-component ordering (which should be reversed upon shutdown).

This is related to #7014

---

1 votes, 1 watchers

[spring-projects-issues]

Juergen Hoeller commented

Since 2.5.2, we already follow the bean dependencies graph when propagating start/stop. So traditional bean references or depends-on specifications should work fine for defining lifecycle dependencies as well... This seems to be of sufficient power - and more natural than relying on the Ordered interface for this specific purpose.

Juergen