Skip to content
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

WELD-2763 Correct how Weld chooses proxy package when a bean has unassignable interface type #2895

Merged
merged 1 commit into from
Oct 20, 2023

Conversation

manovotn
Copy link
Contributor

JIRA with more details - https://issues.redhat.com/browse/WELD-2763
Original issue that started this investigation - jakartaee/platform-tck#1194

@manovotn manovotn changed the title WELD-2763 Correct how Weld chooses proxy package for EJB beans using @Local WELD-2763 Correct how Weld chooses proxy package when a bean has unassignable interface type Oct 19, 2023
@manovotn
Copy link
Contributor Author

I have identified a case where this is reproducible on Weld as well - a user can define a CDI bean and then tweak it's set of types via ProcessBeanAttributes and add an interface that the bean doesn't directly implement. This will trigger the original error as well even in tests without container.

I've added such test and modified the code comment to clarify when this code path occurs

@manovotn manovotn merged commit 9b8671d into weld:master Oct 20, 2023
12 checks passed
@manovotn manovotn deleted the weld2763 branch October 20, 2023 10:40
alwin-joseph added a commit to alwin-joseph/core that referenced this pull request Oct 23, 2023
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.

1 participant