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

Specify that duplicate type discovery is non-portable #571

Merged
merged 1 commit into from
Dec 2, 2021

Conversation

Ladicek
Copy link
Contributor

@Ladicek Ladicek commented Dec 2, 2021

This is because ScannedClasses may be implemented on top of
Portable Extensions using BeforeBeanDiscovery.addAnnotatedType,
which doesn't specify what happens when the same identifier
is used multiple times, and doesn't provide a portable way
to "override" the type that was discovered by the container.

This is because `ScannedClasses` may be implemented on top of
Portable Extensions using `BeforeBeanDiscovery.addAnnotatedType`,
which doesn't specify what happens when the same identifier
is used multiple times, and doesn't provide a portable way
to "override" the type that was discovered by the container.
@manovotn manovotn merged commit c80f9e8 into jakartaee:master Dec 2, 2021
@Ladicek Ladicek deleted the scanned-classes-duplicity branch December 2, 2021 15:16
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.

3 participants