Skip to content

make private methods protected in DefaultLifecycleProcessor for extension [SPR-6617] #11283

@spring-projects-issues

Description

@spring-projects-issues

Matt Goldspink opened SPR-6617 and commented

We have a use case where we'd like to be able to stop and start all SmartLifecycle beans that implement a specific interface but in the correct order using JMX. The DefaultLifecycleProcessor could be extended for our use case and we would simply override the getLifecycleBeans() method and return the subset of beans that meet our requirements. It would be great if this method could be made protected to allow for this kind of extension.


Affects: 3.0 GA

Referenced from: commits 431fd5b

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions