Skip to content

bugfix(jakarta-ee): missing cache entry for the check - #2861

Open
lprimak wants to merge 1 commit into
apache:mainfrom
lprimak:add-form-cache-entry
Open

bugfix(jakarta-ee): missing cache entry for the check#2861
lprimak wants to merge 1 commit into
apache:mainfrom
lprimak:add-form-cache-entry

Conversation

@lprimak

@lprimak lprimak commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Recent fixes missed a code path, so NPE was found, This fixes it

Following this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a GitHub issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a GitHub issue. Your pull request should address just this issue, without pulling in other changes.
  • Format the pull request title like [#XXX] - Fixes bug in SessionManager,
    where you replace #XXX with the appropriate GitHub issue. Best practice
    is to use the GitHub issue title in the pull request title and in the first line of the commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • add fixes #XXX if merging the PR should close a related issue.
  • Run mvn verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
  • Committers: Make sure a milestone is set on the PR
  • Committers: Use "Squash and Merge" to combine all commits into one when merging a PR when appropriate.

Trivial changes like typos do not require a GitHub issue (javadoc, comments...).
In this case, just format the pull request title like [DOC] - Add javadoc in SessionManager.

If this is your first contribution, you have to read the Contribution Guidelines

If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@lprimak lprimak self-assigned this Aug 17, 2026
@lprimak lprimak added this to the 3.0.1 milestone Aug 17, 2026
@github-actions github-actions Bot added the java Pull requests that update Java code label Aug 17, 2026
@lprimak
lprimak marked this pull request as draft August 17, 2026 01:54
@lprimak
lprimak force-pushed the add-form-cache-entry branch from 82a4ecf to 72e52d2 Compare August 17, 2026 02:50
@lprimak
lprimak marked this pull request as ready for review August 17, 2026 02:51
@lprimak
lprimak force-pushed the add-form-cache-entry branch from bf42a47 to a4eaccf Compare August 17, 2026 03:19
@lprimak
lprimak force-pushed the add-form-cache-entry branch from a4eaccf to 11d12a1 Compare August 17, 2026 03:27
Subject subject = methods.getSubject(request, response);
boolean isAuthenticated = subject.isAuthenticated() && subject.getPrincipal() != null;
return isAuthenticated || (useRemembered && subject.isRemembered());
return isAuthenticated || (useRemembered && subject.isRemembered())

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For logic like this, it would be nice to have a unit test targeting this code and triggering the NPE when the fix is not in place.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(or: if the NPE wasn't here, a test that replicates the NPE stack trace. I usually make such tests as simple as possible with as much mocking as possible, targeting own code)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants