-
Notifications
You must be signed in to change notification settings - Fork 306
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
bugfix: Split CDI bean deployment when multiple WARs exist in an EAR #7032
base: main
Are you sure you want to change the base?
Conversation
@Pandrex247 Do you think you can run the TCK against this PR? Thank you! |
@lprimak I ran it through the CDI and EJB TCKs and all seems green 👍 |
Thanks, Fantastic! |
appserver/web/weld-integration/src/main/java/org/glassfish/weld/WeldDeployer.java
Outdated
Show resolved
Hide resolved
…I-enabled library JARs
1c8a517
to
93071cf
Compare
I have found a few issues that I found with "real" applications. |
I may also roll a fix for #6405 if that's trivial as well |
- de-duplicate BDAs in CDI processing by using LinkedHashSet intead of ArrayList - correctly copy BDA sets for each war in EAR - Make WAR's CDI beans available in EAR-libs - made some structures final (cleanup)
a00f107
to
4c255ef
Compare
89ef769
to
4a79348
Compare
Im getting close. "Real" application runs. |
61c4079
to
2471951
Compare
Description
Bugfix. BeanManager isn't properly retrieved when multiple CDI WARs exist in an EAR.
fixes #7031
also fixes #7078
Appears specifically when multiple WARs use OmniFaces
Important Info
** Works and tests pass, but needs more testing to see if all the issues are actually fixed **
Testing
Tested with the failing reproducer
** Needs TCK run
Needs testing with a realistic EAR application, which is still TODO