Skip to content

Fix identity of BindingFacesMessage#5540

Merged
arjantijms merged 1 commit into4.1from
fix_BindingFacesMessage_identity
Dec 26, 2024
Merged

Fix identity of BindingFacesMessage#5540
arjantijms merged 1 commit into4.1from
fix_BindingFacesMessage_identity

Conversation

@BalusC
Copy link
Copy Markdown
Contributor

@BalusC BalusC commented Dec 26, 2024

Fix identity of BindingFacesMessage; it broke since introduction of equals/hashCode for FacesMessage in
jakartaee/faces#1823

Reproducer: trigger 2 different bean validation errors on the same property, it should show 2 separate messages instead of only the last one.

Discovered while analyzing o:validateBean IT failure since switching from Mojarra 4.0.x to 4.1.x.

equals/hashCode for FacesMessage in
jakartaee/faces#1823
Reproducer: trigger 2 different bean validation errors on the same
property
@BalusC BalusC requested review from arjantijms and mnriem December 26, 2024 16:39
@arjantijms arjantijms merged commit 93934ed into 4.1 Dec 26, 2024
@BalusC BalusC deleted the fix_BindingFacesMessage_identity branch December 28, 2024 12:50
BalusC added a commit that referenced this pull request Dec 28, 2024
BalusC added a commit to jakartaee/faces that referenced this pull request Dec 28, 2024
@mnriem
Copy link
Copy Markdown
Contributor

mnriem commented Jan 2, 2025

As you are fixing a bug I would have expected to see a test. Did I miss it?

@BalusC
Copy link
Copy Markdown
Contributor Author

BalusC commented Jan 3, 2025

Nope, there is no test.

I would also have added a test but the TCK situation was super frustrating at that moment.

As the PR is apparently already merged I will add it later via jakartaee/faces#1996

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants