Skip to content

Clarify CompositePropertySource behavior for EnumerablePropertySource contract #34886

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jhoeller opened this issue May 13, 2025 · 0 comments
Closed
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: documentation A documentation task
Milestone

Comments

@jhoeller
Copy link
Contributor

After #17385, the CompositePropertySource javadoc is out of sync since it did not get updated along with the change. It needs to mention that getPropertyNames() fails with an IllegalStateException against any non-EnumerablePropertySource now.

@jhoeller jhoeller added this to the 6.2.7 milestone May 13, 2025
@jhoeller jhoeller self-assigned this May 13, 2025
@jhoeller jhoeller added type: documentation A documentation task in: core Issues in core modules (aop, beans, core, context, expression) for: backport-to-6.1.x Marks an issue as a candidate for backport to 6.1.x labels May 13, 2025
@github-actions github-actions bot added status: backported An issue that has been backported to maintenance branches and removed for: backport-to-6.1.x Marks an issue as a candidate for backport to 6.1.x labels May 13, 2025
jhoeller added a commit that referenced this issue May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: documentation A documentation task
Projects
None yet
Development

No branches or pull requests

1 participant