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

EAR jars are not scanned for annotations #30476

Open
tbitonti opened this issue Jan 3, 2025 · 0 comments
Open

EAR jars are not scanned for annotations #30476

tbitonti opened this issue Jan 3, 2025 · 0 comments

Comments

@tbitonti
Copy link
Contributor

tbitonti commented Jan 3, 2025

This issue is to prototype fixes to module annotation scans, which currently do not scan EAR jars for annotations.

The problem was discovered when migrating an application from TWAS, which does scan EAR jars, to Liberty.

The updates are:

(1) Create a FAT which recreates the issue, and which will document the problem.
(2) Add an application configuration attribute which will enable scans of EAR jars.
(3) Update container servers Module Annotations to add EAR jars to annotation scanning class paths.

There are several points of discussion for this update:

(1) The update will be a change of behavior to existing Liberty installations.
(2) The problem was not noted by any current or previous Liberty installation.
(3) The problem was noted specifically for migration of applications from TWAS to Liberty.
(4) The application structure which gives rise to the problem is unusual.
(5) The correct behavior is not clearly defined by JavaEE or Jakarta specifications.
(6) Adding EAR jars to discovery scans will have a performance impact if many jars are added.

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

No branches or pull requests

1 participant