Skip to content

FileSystemResource does not strictly follow the Resource#isReadable() contract #36584

Closed

Description

@jhoeller

Resource#isReadable() is documented to imply existence. FileSystemResource should strictly follow that contract through a combination of File.exists() and File.canRead calls, performing the former first since it does not require a native call underneath.

Activity

  1. added this to the 7.0.7 milestone on Apr 2, 2026
  2. self-assigned this
    on Apr 2, 2026
  3. added
    in: coreIssues in core modules (aop, beans, core, context, expression)
    for: backport-to-7.0.xMarks an issue as a candidate for backport to 7.0.x
    on Apr 2, 2026
  4. added
    status: backportedAn issue that has been backported to maintenance branches
    and removed
    for: backport-to-7.0.xMarks an issue as a candidate for backport to 7.0.x
    on Apr 2, 2026
  5. added a commit that references this issue on Apr 2, 2026
    e977bd7
  6. added a commit that references this issue on Apr 2, 2026
    684b1e8
  7. added a commit that references this issue on Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)status: backportedAn issue that has been backported to maintenance branchestype: bugA general bug

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions