You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: