Skip to content

Simplify collection of backing bean list for PluginRegistry instances #108

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

Closed
odrotbohm opened this issue Feb 13, 2025 · 0 comments
Closed
Assignees
Milestone

Comments

@odrotbohm
Copy link
Member

No description provided.

@odrotbohm odrotbohm added this to the 4.0 M1 milestone Feb 13, 2025
@odrotbohm odrotbohm self-assigned this Feb 13, 2025
odrotbohm added a commit that referenced this issue Feb 13, 2025
… instances.

We now use the API newly introduced in Spring Framework 6.2.3 / 7.0 M2 to select filtered bean instances from an ObjectProvider (via ….stream(Predicate<Class<?>> filter)). This allows us to avoid having to proxy a List as the ultimate target for the plugin registry. Instead, we can switch to a simple Supplier (SingletonSupplier in particular) to delay the actual bean lookup.

String first pass of refactorings and reducing the exposure of intermediate types previously necessary to also be able to handle the ability to inject lists of beans (see GH-107). Also remove the previously AOT runtime hints registration.
odrotbohm added a commit that referenced this issue Feb 14, 2025
…ionContextAware and Initializing bean.

We now implement the aforementioned interfaces again in deprecated form to allow the new arrangement to be a drop-in replacement for the old approach.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant